From cb6e609372f7272c3c961a1cee353d471114884b Mon Sep 17 00:00:00 2001 From: Slimane ALI Date: Fri, 26 Sep 2025 14:37:49 +0200 Subject: [PATCH 01/23] order_freecertificate update Harmonized FR/EN version and made some edits for clarity purposes. --- .../order_freecertificate/guide.en-gb.md | 81 ++++++++++++------- .../order_freecertificate/guide.fr-fr.md | 25 +++--- 2 files changed, 66 insertions(+), 40 deletions(-) diff --git a/pages/network/load_balancer/order_freecertificate/guide.en-gb.md b/pages/network/load_balancer/order_freecertificate/guide.en-gb.md index 1a7978f30a2..13f3ee9709e 100644 --- a/pages/network/load_balancer/order_freecertificate/guide.en-gb.md +++ b/pages/network/load_balancer/order_freecertificate/guide.en-gb.md @@ -2,30 +2,59 @@ title: Order a free SSL certificate universe: cloud excerpt: Order a free SSL certificate for your web services behind a Load Balancer -updated: 2022-03-29 +updated: 2025-09-26 --- -## Presentation -The OVH Load Balancer service can be configured to support SSL termination.. +## Objective -The purpose of SSL termination is to decrypt the incoming encrypted stream before forwarding it to the appropriate service (web server for example). +The OVH Load Balancer service can be configured to support SSL termination. -SSL termination has a cost for the service that manages it. Rather than letting your servers do it, it is possible to configure your OVH Load Balancer service to do it. +The purpose of SSL termination is to decrypt the incoming encrypted stream before forwarding it to the appropriate service, such as a web server. -Moreover, all your certificates are centralized in one place and their maintenance is easier. +Handling SSL termination on the Load Balancer reduces the computational load on your backend servers and centralizes certificate management. This makes maintenance and security updates easier. -## Configuring the frontend for SSL termination -The first thing to do is to configure your frontend to handle SSL termination. +**Discover how to order a free SSL certificate via the OVHcloud Manager or the API.** + +## Requirements + +- You must have an [OVHcloud Load balancer](/links/network/load-balancer) in your OVHcloud account. +- You must be logged in to the [OVH Control Panel](/links/manager). + +## Instructions ### Via the Manager -In the `Frontends` section of your Manager, click on the `Add Frontend`{.action} button to create a new frontend. An edit window will appear, select the `HTTPS` protocol. You will also need to fill in the `Default Close` or `HTTPS Redirection` field in the advanced settings.. + +#### Configure the frontend for SSL termination + +To enable SSL termination, you must first configure your frontend. + +You can configure your SSL termination from the [OVHcloud Control Panel](/links/manager) in the `Bare Metal Cloud`{.action} section, then `Load Balancer`{.action}. + +After selecting the Load Balancer you wish to modify, create a new frontend or edit an existing one. + +In the `Frontends`{.action} section, click on the `Add Frontend`{.action} button to create a new frontend.
+In the configuration window that opens, select the `HTTPS` protocol. Then, select the `Default server cluster`.
+Finally, open the advanced settings and fill in the `HTTPS Redirection` field. ![Configuring the SSL termination of a Frontend](images/enable_ssl_terminaison.png){.thumbnail} -Once the frontend has been created, you will be prompted to `Apply configuration`{.action} to apply your changes to the relevant area. +Once the frontend has been created, a banner will appear prompting you to `Apply configuration` to deploy your changes in the appropriate zone. + +#### Order the free SSL certificate + +In the `SSL Certificates` section of your Manager, click the `Order SSL Certificate`{.action} button to create a new one. An edit window will appear with an `FQDN` field to be filled in. + +![Add a free SSL certificate](images/iplb-order-ssl.png){.thumbnail} + +#### Follow-up of the order + +In the `Tasks`{.action} section of your Manager, the tasks related to ordering a free SSL Certificate are of the type `orderFreeCertificate`. ### Via API -In the API, the SSL termination is specified by the ssl boolean: (Don't forget to set defaultFarmId or redirectLocation) + +#### Configuring the frontend for SSL termination + +In the API, the SSL termination is specified by the `ssl` boolean. To enable SSL termination, set this parameter to `true`, then set the `defaultFarmId` or `redirectLocation` to the corresponding values. > [!api] > @@ -39,42 +68,36 @@ Then apply the changes : > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh > -## Order the free SSL certificate - -### Via the Manager -In the `SSL Certificates` section of your Manager, click the `Order SSL Certificate`{.action} button to create a new one. An edit window will appear with an `FQDN` field to be filled in. - -![Add a free SSL certificate](images/iplb-order-ssl.png){.thumbnail} - -### Via API -In the API, the command is as follows. For the order to be finalized, the chosen domain name must point to your OVH Load Balancer service. +#### Order the free SSL certificate +In the API, the command is as follows : > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/freeCertificate > -## Follow-up of the order +For the order to be finalized, the chosen domain name must point to your OVH Load Balancer service. -### Via the Manager -In the `Tasks`{.action} section of your Manager, the tasks related to ordering a free SSL Certificate are of the type `orderFreeCertificate`. +#### Follow-up of the order -### Via API +- Returning the task list -#### Return to task list -You can specify the action type orderFreeCertificate to refine the search. +You can specify the action type `orderFreeCertificate` to refine the search. > [!api] > > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/task > -#### Returning the status of a particular stain +- Returning the status of a particular task > [!api] > > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/task/{id} > -## Delivery of the free SSL certificate -Once the order is complete, the SSL Certificate is automatically installed on your OVH Load Balancer service.. +Once the order is complete, the SSL Certificate is automatically installed on your OVH Load Balancer service. + +## Go further + +Join our [community of users](/links/community). diff --git a/pages/network/load_balancer/order_freecertificate/guide.fr-fr.md b/pages/network/load_balancer/order_freecertificate/guide.fr-fr.md index 0922f947f32..1001e8af786 100644 --- a/pages/network/load_balancer/order_freecertificate/guide.fr-fr.md +++ b/pages/network/load_balancer/order_freecertificate/guide.fr-fr.md @@ -2,15 +2,16 @@ title: "Commande d'un certificat SSL gratuit" universe: cloud excerpt: Commander un certificat SSL gratuit pour vos services web derrière un Load Balancer -updated: 2022-03-29 +updated: 2025-09-26 --- ## Objectif -Le service OVHcloud Load Balancer peut être configuré pour prendre en charge la terminaison SSL.
-La terminaison SSL a pour but de déchiffrer le flux chiffré entrant avant de le faire suivre vers le service approprié (serveur web par exemple).
-La terminaison SSL a un coût pour le service qui le gère. Plutôt que de laisser vos serveurs la gérer, vous pouvez configurer votre service OVHcloud Load Balancer afin qu'il s'en charge.
-Par ailleurs, tous vos certificats sont ainsi centralisés au même endroit et leur maintenance s'en trouve facilitée. +Le service OVH Load Balancer peut être configuré pour prendre en charge la terminaison SSL. + +La terminaison SSL a pour but de déchiffrer le flux chiffré entrant avant de le faire suivre vers le service approprié, tel qu'un serveur web. + +Le traitement de la terminaison SSL sur le Load Balancer réduit la charge de calcul sur vos serveurs backend et centralise la gestion des certificats. Cela facilite la maintenance et les mises à jour de sécurité. **Découvrez comment commander un certificat SSL gratuit depuis votre espace client OVHcloud ou via l'API OVHcloud.** @@ -30,12 +31,12 @@ Vous pouvez configurer votre terminaison SSL depuis l'[espace client OVHcloud](/ Après avoir sélectionné le Load Balancer que vous souhaitez modifier, créez un nouveau frontend ou éditez-en un existant. Dans l'onglet `Frontends`{.action}, cliquez sur le bouton `Ajouter un frontend`{.action} pour en créer un nouveau.
-Une fenêtre d'édition apparait alors, sélectionnez le protocole `HTTPS`.
-Renseignez également les champs `Ferme par défaut` ou `Redirection HTTP` dans les paramètres avancés. +Une fenêtre d'édition apparait alors, sélectionnez le protocole `HTTPS`. Ensuite, renseignez le champ `Ferme par défaut`.
+Enfin, ouvrez les paramètres avancés et renseignez le champ `Redirection HTTP`. ![Configuration la terminaison SSL d'un Frontend](images/enable_ssl_terminaison.png){.thumbnail} -Une fois le frontend créé, il vous sera proposé d'`Appliquer la configuration`{.action} pour appliquer vos changements dans la zone concernée. +Une fois le frontend créé, une bannière apparaîtra vous invitant à `Appliquer la configuration`{.action} pour déployer vos changements dans la zone concernée. #### Commander le certificate SSL gratuit @@ -49,9 +50,9 @@ Vous pourrez suivre votre commande dans l'onglet `Tâches`{.action}. La tâche c ### Depuis l'API OVHcloud -#### Commander le certificate SSL gratuit +#### Configurer le frontend pour la terminaison SSL -Dans l'API, la terminaison SSL est spécifiée par le booléen ssl (n'oubliez pas de renseigner `defaultFarmId` ou `redirectLocation`) : +Dans l'API, la terminaison SSL est spécifiée par le booléen `ssl`. Pour activer la terminaison SSL, réglez ce paramètre sur `true`, puis définissez `defaultFarmId` ou `redirectLocation` avec les valeurs correspondantes. > [!api] > @@ -65,6 +66,8 @@ Appliquez ensuite les modifications : > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh > +#### Commander le certificat SSL gratuit + Dans l'API, la commande se fait via l'appel suivant : > [!api] @@ -72,7 +75,7 @@ Dans l'API, la commande se fait via l'appel suivant : > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/freeCertificate > -Pour que la commande se finalise, il faut obligatoirement que le nom de domaine choisi pointe vers votre service OVHcloud Load Balancer. +Pour que la commande soit finalisée, il faut obligatoirement que le nom de domaine choisi pointe vers votre service OVHcloud Load Balancer. #### Suivi de la commande From b13874308e9c18252d46d8c255690da54e591de9 Mon Sep 17 00:00:00 2001 From: Slimane ALI Date: Thu, 16 Oct 2025 21:10:24 +0200 Subject: [PATCH 02/23] blue-green update Updated to use a more professional tone across the document. --- .../case_blue_green/guide.en-gb.md | 64 ++--- .../case_blue_green/guide.fr-fr.md | 260 +++++++++--------- 2 files changed, 160 insertions(+), 164 deletions(-) diff --git a/pages/network/load_balancer/case_blue_green/guide.en-gb.md b/pages/network/load_balancer/case_blue_green/guide.en-gb.md index 3126cb4f2f5..d5ee4f7a18b 100644 --- a/pages/network/load_balancer/case_blue_green/guide.en-gb.md +++ b/pages/network/load_balancer/case_blue_green/guide.en-gb.md @@ -1,56 +1,54 @@ --- title: 'Deploying a blue-green infrastructure' -excerpt: 'This guide will show you how to deploy a blue-green infrastructure with the OVH Load Balancer' +excerpt: 'This guide will show you how to deploy a blue-green infrastructure with the OVHcloud Load Balancer' updated: 2019-02-25 --- ## Objective -With this guide, we will explore a specific use for the OVH Load Balancer service — configuring a service to manage production/development infrastructures easily. This is also called a blue-green infrastructure. +This guide demonstrates a specific use case for the OVHcloud Load Balancer: the configuration of a service to facilitate seamless traffic switching between production and new production candidate environments, also called a `blue-green`{.action} infrastructure. With a `blue-green`{.action} infrastructure, you can stop your infrastructure from experiencing any downtime. The main benefit of this deployment type is that you can prepare updates and/or maintenance in an environment that is isolated from your production environment. This way, you can test your changes before they are put into production, undo them quickly if you detect any faults, and do all of this with virtually zero downtime. -**This guide will show you how to deploy a blue-green infrastructure with the OVH Load Balancer.** +**This guide will show you how to deploy a blue-green infrastructure with the OVHcloud Load Balancer.** ## Requirements To deploy a `blue-green`{.action} infrastructure, you need the following components: -- an OVH Load Balancer service -- a first server that hosts your production infrastructure -- a second server with a similar infrastructure, dedicated to development +- An OVHcloud [Load Balancer](/links/network/load-balancer) service +- Access to the [OVHcloud Control Panel](/links/manager) +- Two [dedicated servers](/links/bare-metal/bare-metal) : one hosting your production environment, and a similarly configured server hosting your development environment. ## Instructions ### Scenario -The scenario we’ll describe here is as follows... +You have an infrastructure designed to host your live website. -You have an infrastructure that you can use to put your website online. - -This infrastructure hosts your website’s code, and it also hosts the applications (web servers, database servers, etc.) required to put your website online. You need to update your applications and/or your code on a regular basis. You want to be able to test your updates without the risk of affecting your website’s availability to customers, or stopping the website from working properly. +This environment hosts the website’s code, in addition to all essential applications (web servers, database servers, etc.). You need to update your applications and/or your code on a regular basis. You want to be able to test your updates without impacting the website's availability or functionality for end-users. One way to achieve this is by deploying a `blue-green`{.action} infrastructure. -The principle of a `blue-green`{.action} deployment involves being able to switch easily from a development infrastructure to a production infrastructure, and vice versa. This switch must be done in a way that is transparent for your users. To do this, we will assign the standard HTTP port 80 for access to the production infrastructure, and the arbitrary port 8888 to access the development infrastructure. +The principle of a `blue-green`{.action} deployment involves being able to switch easily from a development infrastructure to a production infrastructure, and vice versa. This switch must be done in a way that is transparent for your users. To do this, public traffic will be routed to the standard HTTP port 80 for access to the production infrastructure, and a non-standard port, such as 8888, will be used to access the development infrastructure. -## Deploy the infrastructures. +## Deploy the infrastructures -In the scenario we are using, your IP Load Balancer service plays a central role. It is the element you use to expose your two infrastructures (production and development) to different users at the same time. +In this scenario, your Load Balancer service plays a central role. It is the element you use to expose your two infrastructures (production and development) to different users at the same time. The production infrastructure can be accessed by your customers on the standard HTTP service (port 80), and your development infrastructure can be accessed by developers and admins on the non-standard port 8888. -During the initial setup phase, we will arbitrarily assign a role to each of the parts of our infrastructure. `Infrastructure A`{.action} will be assigned to production, while `infrastructure B`{.action} will be assigned to development. At this stage, we will consider them to be similar to one another. +During the initial setup phase, roles are provisionally assigned to each infrastructure component. `Infrastructure A`{.action} serves as the initial production environment, while `infrastructure B`{.action} serves as the staging environment. At this stage, we will consider them to be similar to one another. -A `blue-green`{.action} infrastructure involves switching from infrastructure A to infrastructure B, when infrastructure B is ready to expose your website after your changes have been applied and tested. The IP Load Balancer will manage this switch. +A `blue-green`{.action} infrastructure involves switching from infrastructure A to infrastructure B, once infrastructure B has been fully updated and validated. The Load Balancer will manage this switch. The diagram below gives a general idea of the architecture: ![General diagram of blue-green architecture](images/scheme.png){.thumbnail} -### Infrastructure A. +### Infrastructure A -This infrastructure is made up of a server farm that will later be associated with a front-end of your IP Load Balancer. This farm will expose an HTTP, TCP or UDP service to the front-end. It also balances loads by sending the front-end’s incoming traffic to the servers. For more detail on the role of various component of the OVH Load Balancer service, you can read the following guide: [Introduction to the OVH Load Balancer](/pages/network/load_balancer/use_presentation). +This infrastructure is made up of a server farm that will later be associated with a front-end of your Load Balancer. This farm will expose an HTTP, TCP or UDP service to the front-end. It also balances loads by sending the front-end’s incoming traffic to the servers. For more detail on the role of various component of the OVHcloud Load Balancer service, you can read the following guide: [Introduction to the OVHcloud Load Balancer](/pages/network/load_balancer/use_presentation). In our scenario, we will declare a farm of servers for the HTTP service. Please note that you can create as many farms (as well as TCP and/or UDP services) as are required for your final service to be exposed to your customers. @@ -126,9 +124,9 @@ With the additional calls listed below, you can list, modify and delete your ser > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/http/farm/{farmId}/server > -### Infrastructure B. +### Infrastructure B -Functionally, this second infrastructure is identical to the first. It is also composed of a server farm that will later be associated with a second front-end of your IP Load Balancer. This server farm exposes the same service to the front-end as the first server farm. This service is supplied on the servers by port 8080. +Functionally, this second infrastructure is identical to the first. It is also composed of a server farm that will later be associated with a second front-end of your Load Balancer. This server farm exposes the same service to the front-end as the first server farm. This service is supplied on the servers by port 8080. Deploy the server farm for the HTTP service (and/or any other TCP or UDP services required for your final service to be exposed to your customers). @@ -176,7 +174,7 @@ At this stage, here is the configuration status for your two farms: ![Farm configuration](images/farms.png){.thumbnail} -## Front-ends. +## Front-ends The magic of `blue-green`{.action} deployment lies in the configuration of your front-ends. At this stage, we have configure two functionally identical infrastructures. For both infrastructures, you have declared one or more server farms, each with their own set of associated servers. @@ -189,7 +187,7 @@ To do this, we need to declare two front-ends. The first one will give you acces > If the final service you expose to your customers requires several server farms (e.g. ports 80 and 443), you will need to declare a `front-end`{.action} for each of your farms. > -### Blue front-end. +### Blue front-end This `front-end`{.action} is dedicated to accessing the production infrastructure. The ports exposed to your customers are the standard ports for accessing the service. In this case, we are exposing a HTTP service, so we will use port 80 (443 if you would like an SSL termination). #### Via the OVH Control Panel: @@ -213,7 +211,7 @@ This `front-end`{.action} is dedicated to accessing the production infrastructur |port|Required|The port exposed to your customers by your front-end|80| |zone|Required|The zone in which you want to deploy your front-end|all| -### Green front-end. +### Green front-end This `front-end`{.action} is dedicated to accessing the development infrastructure. The ports exposed to your customers will be non-standard ports that you can choose arbitrarily. In this case, we will expose the HTTP development service on port 8888. @@ -238,11 +236,11 @@ This `front-end`{.action} is dedicated to accessing the development infrastructu |port|Required|The port exposed to your customers by your front-end|8888| |zone|Required|The zone in which you want to deploy your front-end|all| -## Manage the deployments. +## Manage the deployments -### Initial deployment. +### Initial deployment -Once you have finished configuring the components of the OVH Load Balancer service, you now just need to apply your changes. +Once you have finished configuring the components of the OVHcloud Load Balancer service, you now just need to apply your changes. #### Via the OVH Control Panel: @@ -259,11 +257,11 @@ Once you have finished configuring the components of the OVH Load Balancer servi |---|---| |serviceName|Your Load Balancer service ID| -### The production/pre-production switch. +### The production/staging switch -At this stage, our initial environment is deployed and ready to use. How do we use it? +At this stage, our initial environment is deployed and ready to use. -To put it simply, you just need to switch over your front-ends from one server farm to another. +Now, you need to switch over your front-ends from one server farm to another. Let’s take a look at our scenario: @@ -317,12 +315,16 @@ This should be the result on the Sunrise Control Panel after updating the front- |---|---| |serviceName|Your Load Balancer service ID| -## Go further +## Conclusion -You now have an infrastructure you can use to simply and efficiently manage `blue-green deployments`{.action}. +You have successfully implemented a highly available infrastructure for managing `blue-green deployments`{.action}. -Developers have access to a development environment on port 8888 (or whichever other port you would prefer to define), while your customers continue to access the service in production via the standard HTTP port (80 in our case, for example). +Developers have access to a development environment on port 8888 (or any configurable non-standard port), while your customers continue to access the service in production via the standard HTTP port (80). The infrastructure presented here is limited to just one port, but it can be expanded by adding other ports. For example, you can also expose your website on the standard HTTPS port (443). You can do this by defining new farms dedicated to each port you want to expose, and associating them with their corresponding front-ends (one for the standard port exposed in production, the second for the arbitrary port dedicated to development). Another way to consolidate your infrastructure even further is by multiplying the servers attached to your farms. This way, you can make your services more redundant (guaranteeing availability as a result), and also add a load balancing capacity. + +## Go further + +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/case_blue_green/guide.fr-fr.md b/pages/network/load_balancer/case_blue_green/guide.fr-fr.md index 49ce58f18df..3f87ee3fc8e 100644 --- a/pages/network/load_balancer/case_blue_green/guide.fr-fr.md +++ b/pages/network/load_balancer/case_blue_green/guide.fr-fr.md @@ -1,74 +1,73 @@ --- -title: Infrastructure Blue-Green -excerpt: Cas pratique -updated: 2022-04-26 +title: "Déploiement d'une infrastructure blue-green" +excerpt: "Ce guide vous montre comment déployer une infrastructure blue-green avec le Load Balancer OVHcloud" +updated: 2019-02-25 --- ## Objectif -Ce guide a pour but de vous aider à explorer un cas d'usage particulier de votre service OVHcloud Load Balancer : configurer son service pour gérer facilement une infrastructure production / développement également appelée **Blue-Green**. +Ce guide présente un cas d'usage spécifique du service Load Balancer OVHcloud : la configuration d'un service visant à faciliter le basculement fluide du trafic entre l'environnement de production et un nouvel environnement candidat à la production, également appelé infrastructure `blue-green`{.action}. -Un déploiement **Blue-Green** permet de s'affranchir du temps d'indisponibilité de votre infrastructure. L'intérêt principal est que ce type de déploiement vous offre la possibilité de préparer vos mises à jour et / ou maintenances dans un environnement isolé de votre environnement de production. Vous pouvez ainsi tester vos modifications avant leur mise en production mais aussi revenir rapidement en arrière en cas de détection d'un dysfonctionnement, tout ceci avec des délais d'indisponibilité quasiment nuls. +Une infrastructure `blue-green`{.action} vous permet d'éviter toute interruption de service de votre infrastructure. Le principal avantage de ce type de déploiement est de pouvoir préparer des mises à jour et/ou des opérations de maintenance dans un environnement isolé de votre environnement de production. Vous pouvez ainsi tester vos modifications avant la mise en production, les annuler rapidement en cas de détection de défaillances, et ce, avec une interruption de service quasi nulle. + +**Ce guide vous montre comment déployer une infrastructure blue-green avec le Load Balancer OVHcloud.** ## Prérequis -Pour mettre en oeuvre un déploiement de type **Blue-Green**, vous devez disposer des éléments suivants : +Pour déployer une infrastructure `blue-green`{.action}, vous avez besoin des composants suivants : -- Posséder une offre [OVHcloud Load balancer](/links/network/load-balancer) dans votre compte OVHcloud -- Être connecté à votre [espace client OVHcloud](/links/manager) -- Un premier serveur qui porte votre infrastructure de production -- Un second serveur qui porte une infrastructure similaire dédiée au développement +- Un service [Load Balancer](/links/network/load-balancer) OVHcloud +- Un accès au [Panneau de configuration OVHcloud](/links/manager) +- Deux [serveurs dédiés](/links/bare-metal/bare-metal) : un hébergeant votre environnement de production, et un serveur de configuration similaire hébergeant votre environnement de développement. ## En pratique ### Scénario -Le scénario que nous vous proposons ici est le suivant : vous disposez d'une infrastructure qui vous permet de mettre en ligne votre site internet. +Vous disposez d'une infrastructure conçue pour héberger votre site Web en direct. -Cette infrastructure héberge le code de votre site mais aussi les applications (serveurs web, serveurs de base de données, etc.) nécessaires à la mise en ligne du site. Régulièrement vous êtes confronté à la nécessité de mettre à jour vos applications et / ou votre code. Vous souhaitez être en mesure de tester vos mises à jours sans affecter ni la disponibilité, ni le bon fonctionnement du site exposé à vos clients. +Cet environnement héberge le code de votre site Web, ainsi que toutes les applications essentielles (serveurs Web, serveurs de bases de données, etc.). Vous devez mettre à jour vos applications et/ou votre code régulièrement. Vous souhaitez pouvoir tester vos mises à jour sans impact sur la disponibilité ou la fonctionnalité du site Web pour les utilisateurs finaux. -Une solution possible pour atteindre ces objectifs est de mettre en œuvre un déploiement **Blue-Green**. +Une façon d'y parvenir est de déployer une infrastructure `blue-green`{.action}. -Le principe d'un déploiement **Blue-Green** consiste à vous permettre de basculer facilement d'une infrastructure de développement vers une infrastructure de production, et vice-versa. Cette bascule doit pouvoir se faire de manière transparente pour vos différents utilisateurs. Pour ce faire, nous allons assigner le port HTTP standard 80 pour les accès à l'infrastructure de production et le port arbitraire 8888 pour les accès à l'infrastructure de développement. +Le principe d'un déploiement `blue-green`{.action} implique de pouvoir basculer facilement d'une infrastructure de développement à une infrastructure de production, et inversement. Ce basculement doit être transparent pour vos utilisateurs. Pour ce faire, le trafic public sera acheminé vers le port HTTP standard 80 pour l'accès à l'infrastructure de production, et un port non standard, tel que 8888, sera utilisé pour l'accès à l'infrastructure de développement. -### Déployer les infrastructures +## Déploiement des infrastructures -Dans le cadre du scénario proposé, votre service IP Load Balancing joue un rôle central. Il est l'élément qui vous permet d'exposer simultanément vos 2 infrastructures (production et développement) à vos différents utilisateurs. +Dans ce scénario, votre service Load Balancer joue un rôle central. C'est l'élément que vous utilisez pour exposer simultanément vos deux infrastructures (production et développement) à différents utilisateurs. -L'infrastructure de production est accessible à vos clients sur le service HTTP standard (port 80). L'infrastructure de développement quant à elle est accessible à vos développeurs / administrateurs sur le port non-standard 8888. +L'infrastructure de production est accessible par vos clients sur le service HTTP standard (port 80), et votre infrastructure de développement est accessible par les développeurs et administrateurs sur le port non standard 8888. -Durant la phase initiale d'installation, nous allons assigner arbitrairement un rôle à chacune des parties de notre infrastructure. L'**infrastructure A** sera assignée à la production tandis que l'**infrastructure B** sera assignée au développement. Nous considérons qu'à ce stade elles sont similaires. +Au cours de la phase de configuration initiale, les rôles sont provisoirement attribués à chaque composant de l'infrastructure. L'`Infrastructure A`{.action} sert d'environnement de production initial, tandis que l'`infrastructure B`{.action} sert d'environnement de staging. À ce stade, nous allons les considérer comme similaires l'une à l'autre. -Le déploiement **Blue-Green** consiste à basculer de l'infrastructure A vers l'infrastructure B lorsque cette dernière est prête à exposer votre site après que vos changements aient été appliqués et testés. C'est l'IPBL qui se chargera de gérer cette bascule. +Une infrastructure `blue-green`{.action} implique le basculement de l'infrastructure A vers l'infrastructure B, une fois que l'infrastructure B est prête à exposer votre site Web après que vos modifications ont été appliquées et testées. Le Load Balancer gérera ce basculement. -Le schéma suivant détail l'architecture générale : +Le schéma ci-dessous donne une idée générale de l'architecture : -![Schéma général de l'architecture blue-green](images/scheme.png){.thumbnail} +![General diagram of blue-green architecture](images/scheme.png){.thumbnail} ### Infrastructure A -Cette infrastructure est composée d'une ferme de serveurs qui sera ultérieurement associée à un frontend de votre IPLB. Cette ferme expose au frontend un service de type HTTP, TCP ou UDP. Elle se charge également de la répartition de charge en transmettant aux serveurs le trafic reçu par le frontend. Pour plus de précisions sur le rôle des différents éléments du service OVHcloud Load Balancer, vous pouvez vous réferer à cette documentation : [Présentation de l'OVHcloud Load Balancer](/pages/network/load_balancer/use_presentation). - -**Déployer la ferme de serveurs pour le service HTTP :** +Cette infrastructure est composée d'une ferme de serveurs qui sera associée plus tard à un front-end de votre Load Balancer. Cette ferme exposera un service HTTP, TCP ou UDP au front-end. Elle assure également l'équilibrage de charge en envoyant le trafic entrant du front-end aux serveurs. Pour plus de détails sur le rôle des différents composants du service Load Balancer OVHcloud, vous pouvez lire le guide suivant : [Introduction au Load Balancer OVHcloud](/pages/network/load_balancer/use_presentation). -Dans le cadre de notre scénario, nous déclarons une ferme de serveurs pour le service HTTP. À noter que vous pouvez créer autant de fermes que de services TCP et / ou UDP nécessaires au bon fonctionnement du service final exposé à vos clients. +Dans notre scénario, nous allons déclarer une ferme de serveurs pour le service HTTP. Veuillez noter que vous pouvez créer autant de fermes (ainsi que de services TCP et/ou UDP) que nécessaire pour que votre service final soit exposé à vos clients. -Depuis l'espace client OVHcloud : +#### Via le Panneau de configuration OVH : -![Ajout d'une nouvelle ferme HTTP dédié à l'infrastructure A](images/ferme1.png){.thumbnail} +![Add a new HTTP farm dedicated to infrastructure A](images/ferme1.png){.thumbnail} -Depuis l'API OVHcloud : +#### Via l'API : > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/farm > -|Paramètre|Signification| +|Setting|Meaning| |---|---| -|serviceName|L'identifiant de votre service Load Balancer| +|serviceName|Votre ID de service Load Balancer| -Les appels complémentaires suivants vous permettront respectivement de lister, modifier ou supprimer vos fermes. +Avec les appels supplémentaires listés ci-dessous, vous pouvez respectivement lister, modifier et supprimer vos fermes de serveurs. > [!api] > @@ -85,32 +84,30 @@ Les appels complémentaires suivants vous permettront respectivement de lister, > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/http/farm > -**Associer un serveur à votre ferme :** - -Il s'agit ici du serveur physique portant votre infrastructure de production. Le service exposé au frontend est fourni par le port 8080 du serveur. A noter que vous pouvez associer à chaque ferme un ou plusieurs serveurs (par exemple, pour répartir la charge et / ou offrir une meilleur tolérance aux pannes). +Associez un serveur à votre ferme, s'il s'agit d'un serveur physique hébergeant votre infrastructure de production. Le service exposé au front-end est fourni par le port 8080 du serveur. Veuillez noter que vous pouvez associer un ou plusieurs serveurs à chaque ferme (pour équilibrer la charge et/ou offrir une tolérance aux pannes plus élevée, par ex.). -Depuis l'espace client OVHcloud : +#### Via le Panneau de configuration OVH : -![Ajout d'un nouveau serveur à la ferme HTTP A](images/serveur1.png){.thumbnail} +![Add a new server to the farm HTTP A](images/serveur1.png){.thumbnail} -![Renseigner la configuration du serveur HTTP A](images/server1.png){.thumbnail} +![Enter the HTTP A server’s configuration](images/server1.png){.thumbnail} -Depuis l'API OVHcloud : +#### Via l'API : > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/farm/{farmId}/server > -|Paramètre|Requis|Signification|Exemple| +|Setting|Required|Meaning|Example| |---|---|---|---| -|serviceName|Requis|L'identifiant de votre service Load Balancer|loadbalancer-XXXXXXXXXXXXX| -|farmId|Requis|L'identifiant de votre ferme de serveurs|197529| -|address|Requis|L'addresse IPv4 de votre serveur|139.XX.XX.XX| -|displayName||Le nom du serveur associé à votre ferme|Serveur HTTP A| +|serviceName|Requis|Votre ID de service Load Balancer|loadbalancer-abcdef0123456789| +|farmId|Requis|Votre ID de ferme de serveurs|77212| +|address|Requis|L'adresse IPv4 de votre serveur|10.10.1.100| +|displayName||Le nom du serveur associé à votre ferme|HTTP A server| |port||Le port du serveur associé à votre ferme|8080| -Les appels complémentaires suivants vous permettront respectivement de lister, modifier ou supprimer vos serveurs. +Avec les appels supplémentaires listés ci-dessous, vous pouvez respectivement lister, modifier et supprimer vos serveurs. > [!api] > @@ -129,208 +126,205 @@ Les appels complémentaires suivants vous permettront respectivement de lister, ### Infrastructure B -Cette seconde infrastructure est fonctionnellement jumelle de la précédente. Elle est également composée d'une ferme de serveurs qui sera ultérieurement associée à un second frontend de votre IPLB. Cette ferme expose au frontend le même service que la ferme précédemment créée. Ce service est fourni sur les serveurs par le port 8080. +Fonctionnellement, cette deuxième infrastructure est identique à la première. Elle est également composée d'une ferme de serveurs qui sera associée plus tard à un second front-end de votre Load Balancer. Cette ferme de serveurs expose le même service au front-end que la première ferme de serveurs. Ce service est fourni sur les serveurs par le port 8080. -**Déployer la ferme de serveurs pour le service HTTP (et / ou tout autre service TCP ou UDP nécessaire au fonctionnement du service final exposé à vos clients) :** +Déployez la ferme de serveurs pour le service HTTP (et/ou tout autre service TCP ou UDP requis pour que votre service final soit exposé à vos clients). -Depuis l'espace client OVHcloud : +#### Via le Panneau de configuration Sunrise : -![Ajout d'une nouvelle ferme HTTP dédié à l'infrastructure B](images/ferme2.png){.thumbnail} +![Add a new HTTP farm dedicated to infrastructure B](images/ferme2.png){.thumbnail} -![Création d'une seconde ferme dédiée à l'infrastructure B](images/backend2.png){.thumbnail} +![Create a second farm dedicated to infrastructure B](images/backend2.png){.thumbnail} -Depuis l'API OVHcloud : +#### Via l'API : > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/farm > -|Paramètre|Signification| +|Setting|Meaning| |---|---| -|serviceName|L'identifiant de votre service Load Balancer| +|serviceName|Votre ID de service Load Balancer| -**Associer un serveur à votre ferme :** +Associez un serveur à votre ferme. Ici, il s'agit d'un ou plusieurs serveurs physiques hébergeant votre infrastructure de développement. -Il s'agit ici du (ou des) serveur(s) physique(s) portant votre infrastructure de développement. +#### Via le Panneau de configuration OVH : -Depuis l'espace client OVHcloud : +![Add a new server to the farm HTTP B](images/serveur2.png){.thumbnail} -![Ajout d'une nouveau serveur à la ferme HTTP B](images/serveur2.png){.thumbnail} +![Enter the HTTP B server’s configuration](images/server2.png){.thumbnail} -![Renseigner la configuration du serveur HTTP B](images/server2.png){.thumbnail} - -Depuis l'API OVHcloud : +#### Via l'API : > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/farm/{farmId}/server > -|Paramètre|Requis|Signification|Exemple| +|Setting|Required|Meaning|Example| |---|---|---|---| -|serviceName|Requis|L'identifiant de votre service Load Balancer|loadbalancer-XXXXXXXXXXX| -|farmId|Requis|L'identifiant de votre ferme de serveurs|197530| -|address|Requis|L'addresse IPv4 de votre serveur|51.XX.XX.XX| -|displayName||Le nom du serveur associé à votre ferme|Serveur HTTP B| +|serviceName|Requis|Votre ID de service Load Balancer|loadbalancer-abcdef0123456789| +|farmId|Requis|Votre ID de ferme de serveurs|77213| +|address|Requis|L'adresse IPv4 de votre serveur|10.10.2.100| +|displayName||Le nom du serveur associé à votre ferme|HTTP B server| |port||Le port du serveur associé à votre ferme|8080| -À ce stade, voici l'état de la configuration de vos 2 fermes : +À ce stade, voici l'état de la configuration de vos deux fermes : -![Configuration des fermes](images/farms.png){.thumbnail} +![Farm configuration](images/farms.png){.thumbnail} -### Les frontends +## Front-ends -Toute la magie du déploiement **Blue-Green** se situe au niveau de la configuration de vos frontends. A ce stade nous avons configuré 2 infrastructures fonctionnellement jumelles en déclarant, pour chaque infrastructure, une (ou plusieurs) ferme(s) de serveurs, avec pour chaque ferme son (ses) serveur(s) associé(s). +La magie du déploiement `blue-green`{.action} réside dans la configuration de vos front-ends. À ce stade, nous avons configuré deux infrastructures fonctionnellement identiques. Pour les deux infrastructures, vous avez déclaré une ou plusieurs fermes de serveurs, chacune avec son propre ensemble de serveurs associés. -Pour permettre de basculer simplement d'une infrastructure à une autre, nous allons nous servir des frontends. +Pour basculer simplement d'une infrastructure à l'autre, nous utiliserons des front-ends. -Pour cela, nous devons déclarer 2 frontends. Le premier permettra d'accéder à l'infrastructure de production tandis que le second se chargera des accès à l'infrastructure de développement. Les accès à l'une ou l'autre des infrastructures seront controlés grâce aux ports exposés à vos clients. +Pour ce faire, nous devons déclarer deux front-ends. Le premier vous donnera accès à votre infrastructure de production, tandis que le second vous donnera accès à votre infrastructure de développement. Vous pouvez contrôler l'accès à une infrastructure ou à l'autre en utilisant les ports que vous exposez à vos clients. > [!warning] > -> Si le service final exposé à vos clients nécessite plusieurs fermes de serveurs (par exemple : les ports 80 et 443), vous devrez déclarer un **frontend** pour chacune de vos fermes. +> Si le service final que vous exposez à vos clients nécessite plusieurs fermes de serveurs (par ex. les ports 80 et 443), vous devrez déclarer un `front-end`{.action} pour chacune de vos fermes. > -#### Frontend Blue - -Ce **frontend** est dédié aux accès à l'infrastructure de production, les ports exposés à vos clients sont les ports standards d'accès au service. Dans le cas présent, nous exposons un service HTTP. Nous allons donc utiliser le port 80 (443 si vous souhaitez une terminaison SSL). +### Front-end Blue +Ce `front-end`{.action} est dédié à l'accès à l'infrastructure de production. Les ports exposés à vos clients sont les ports standard pour l'accès au service. Dans ce cas, nous exposons un service HTTP, nous utiliserons donc le port 80 (443 si vous souhaitez une terminaison SSL). -Depuis l'espace client OVHcloud : +#### Via le Panneau de configuration OVH : -![Ajout du frontend dédié à la production, Blue Frontend](images/frontend1.png){.thumbnail} +![Adding a front-end dedicated to production, a blue front-end](images/frontend1.png){.thumbnail} -![Renseigner la configuration du frontend Blue](images/fblue.png){.thumbnail} +![Enter the blue front-end’s configuration](images/fblue.png){.thumbnail} -Depuis l'API OVHcloud : +#### Via l'API : > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/frontend > -|Paramètre|Requis|Signification|Exemple| +|Setting|Required|Meaning|Example| |---|---|---|---| -|serviceName|Requis|L'identifiant de votre Load Balancer|loadbalancer-XXXXXXXXXXX| -|defaultFarmId||L'identifiant de la ferme de production|151917| -|displayName||Le nom donné au frontend|Blue Frontend| -|port|Requis|Le port exposé par votre frontend à vos clients|80| -|zone|Requis|La zone dans laquelle vous souhaitez déployer votre frontend|all| +|serviceName|Requis|Votre ID de service Load Balancer|loadbalancer-abcdef0123456789| +|defaultFarmId||Votre ID de ferme de production|77212| +|displayName||Le nom donné au front-end|Blue front-end| +|port|Requis|Le port exposé à vos clients par votre front-end|80| +|zone|Requis|La zone dans laquelle vous souhaitez déployer votre front-end|all| -#### Frontend Green +### Front-end Green -Ce **frontend** est dédié aux accès à l'infrastructure de développement, les ports exposés à vos clients seront des ports non-standards que vous pouvez choisir arbitrairement. Dans le cas présent, nous allons exposer le service HTTP de développement sur le port 8888. +Ce `front-end`{.action} est dédié à l'accès à l'infrastructure de développement. Les ports exposés à vos clients seront des ports non standard que vous pourrez choisir arbitrairement. Dans ce cas, nous exposerons le service de développement HTTP sur le port 8888. -Depuis l'espace client OVHcloud : +#### Via le Panneau de configuration OVH : -![Ajout du frontend dédié au développement, Green Frontend](images/frontend2.png){.thumbnail} +![Add the green front-end, dedicated to development](images/frontend2.png){.thumbnail} -![Renseigner la configuration du frontend Green](images/fgreen.png){.thumbnail} +![Enter the green front-end’s configuration](images/fgreen.png){.thumbnail} -Depuis l'API OVHcloud : +#### Via l'API : > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/frontend > -|Paramètre|Requis|Signification|Exemple| +|Setting|Required|Meaning|Example| |---|---|---|---| -|serviceName|Requis|L'identifiant de votre Load Balancer|loadbalancer-xxxxxxxxxx| -|defaultFarmId||L'identifiant de la ferme de production|151918| -|displayName||Le nom donné au frontend|Green Frontend| -|port|Requis|Le port exposé par votre frontend à vos clients|8888| -|zone|Requis|La zone dans laquelle vous souhaitez déployer votre frontend|all| +|serviceName|Requis|Votre ID de service Load Balancer|loadbalancer-abcdef0123456789| +|defaultFarmId||Votre ID de ferme de production|77213| +|displayName||Le nom donné au front-end|Green front-end| +|port|Requis|Le port exposé à vos clients par votre front-end|8888| +|zone|Requis|La zone dans laquelle vous souhaitez déployer votre front-end|all| -### Gérer les déploiements +## Gestion des déploiements -#### Déploiement initial +### Déploiement initial -Après avoir finalisé la configuration des différents composants de votre service OVHcloud Load Balancer, il ne vous reste plus qu'à appliquer vos changements. +Une fois que vous avez terminé de configurer les composants du service Load Balancer OVHcloud, il ne vous reste plus qu'à appliquer vos modifications. -Depuis l'espace client OVHcloud : +#### Via le Panneau de configuration OVH : -![Appliquer vos changements sur la zone](images/deploy.png){.thumbnail} +![Apply your changes to the zone](images/deploy.png){.thumbnail} -Depuis l'API OVHcloud : +#### Via l'API : > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh > -|Paramètre|Signification| +|Setting|Meaning| |---|---| -|serviceName|L'identifiant de votre service Load Balancer| +|serviceName|Votre ID de service Load Balancer| -#### Bascule production / preproduction +### Basculement production/staging -À ce stade, notre environnement initial est déployé et prêt à être utilisé. Comment l'utiliser ? +À ce stade, notre environnement initial est déployé et prêt à l'emploi. -De manière assez simple, il suffira désormais de basculer vos frontends d'une ferme de serveur à une autre ! +Maintenant, vous devez basculer vos front-ends d'une ferme de serveurs à une autre. -Reprenons notre scénario : +Prenons notre scénario : -- l'infrastructure de production (A) est déployée sur la **Ferme HTTP A** (id 197529) qui est elle même attachée au **Serveur HTTP A**. L'accès à cette infrastructure se fait par l'intermédiaire du **Frontend Blue**. -- l'infrastructure de développement (B) est déployée sur la **Ferme HTTP B** (id 197530) qui est elle même attachée au **Serveur HTTP B**. L'accès à cette infrastructure se fait par l'intermédiaire du **Frontend Green**. +- L'infrastructure de production (A) est déployée sur la `ferme HTTP A`{.action} (id 77212), qui est elle-même attachée au `serveur HTTP A`{.action}. Cette infrastructure est accessible via le `front-end blue`{.action}. +- L'infrastructure de développement (B) est déployée sur la `ferme HTTP B`{.action} (id 77213), qui est elle-même attachée au `serveur HTTP B`{.action}. Cette infrastructure est accessible via le `front-end green`{.action}. -Après avoir réalisé vos modifications / mises à jour sur l'**infrastructure B** et validé le bon fonctionnement du service, vous décidez de l'assigner à la production. +Une fois que vous avez modifié/appliqué les mises à jour à l'`infrastructure B`{.action} et vérifié que le service fonctionne correctement, vous décidez de la mettre en production. -Pour faire la bascule entre les 2 fermes, il suffira simplement de mettre à jour vos différents frontends en modifiant l'identifiant de la ferme à laquelle ils sont rattachés et d'appliquer la modification. +Pour basculer entre les deux fermes, vous pouvez simplement mettre à jour vos différents front-ends en modifiant l'ID de la ferme à laquelle il est attaché, et en appliquant la modification. -Le **Frontend Blue** (id 151917) va donc être associé à la **Ferme B** (infrastructure B, nouvelle production, id 197530). +Le `front-end blue`{.action} (id 70089) sera alors associé à la `Ferme B`{.action} (infrastructure B, nouvelle production, id 77213). -Le **Frontend Green** (id 151918) quant à lui sera désormais associé à la **Ferme A** (infrastructure A, nouveau développement, id 197529). +Le `front-end green`{.action} (id 70090) sera alors associé à la `Ferme A`{.action} (infrastructure A, nouveau développement, id 77212). -Résultat sur l'espace client après la mise à jour des frontends et application de la nouvelle configuration : +Voici le résultat attendu sur le Panneau de configuration Sunrise après la mise à jour des front-ends et l'application de la nouvelle configuration : -![Résultat après la mise à jour des frontends](images/switch.png){.thumbnail} +![Result after updating front-ends](images/switch.png){.thumbnail} -Depuis l'API OVHcloud : mise à jour des frontends et application des modifications +#### Via l'API : mise à jour des front-ends et application des modifications #### > [!api] > > @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/http/frontend/{frontendId} > -|Paramètre|Signification|Exemple| +|Setting|Meaning|Example| |---|---|---| -|ServiceName|L'identifiant de votre service Load Balancer|loadbalancer-xxxxxxxxxxx| -|frontendId|L'identifiant de votre frontend de production|151917| -|defaultFarmId|L'identifiant de votre ferme de serveurs de développement|151918| +|serviceName|Votre ID de service Load Balancer|loadbalancer-abcdef0123456789| +|frontendId|Votre ID de front-end de production|70089| +|defaultFarmId|Votre ID de ferme de serveurs de développement|77213| > [!api] > > @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/http/frontend/{frontendId} > -|Paramètre|Signification|Exemple| +|Setting|Meaning|Example| |---|---|---| -|ServiceName|L'identifiant de votre service Load Balancer|loadbalancer-xxxxxxxxxxx| -|frontendId|L'identifiant de votre frontend de production|151917| -|defaultFarmId|L'identifiant de votre ferme de serveurs de développement|197530| +|serviceName|Votre ID de service Load Balancer|loadbalancer-abcdef0123456789| +|frontendId|Votre ID de front-end de production|70090| +|defaultFarmId|Votre ID de ferme de serveurs de développement|77212| -Utilisez l'appel API suivant pour appliquer vos changements et réaliser effectivement la bascule production / développement : +#### Pour appliquer vos modifications et basculer effectivement les environnements de production et de développement : > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh > -|Paramètre|Signification| +|Setting|Meaning| |---|---| -|serviceName|L'identifiant de votre service Load Balancer| +|serviceName|Votre ID de service Load Balancer| ## Conclusion -Vous disposez désormais d'une infrastructure vous permettant de gérer simplement et efficacement vos déploiements **Blue-Green**. +Vous avez réussi à mettre en œuvre une infrastructure hautement disponible pour la gestion des `déploiements blue-green`{.action}. -Les développeurs disposent d'un accès à l'infrastructure de développement sur le port 8888 (ou tout autre port que vous souhaiteriez définir) tandis que vos clients continuent d'accéder au service en production via le port HTTP standard (80 dans le cas de notre exemple). +Les développeurs ont accès à un environnement de développement sur le port 8888 (ou tout port non standard configurable), tandis que vos clients continuent d'accéder au service en production via le port HTTP standard (80). -L'infrastructure présentée ici se limite à l'exposition d'un seul et unique port, elle peut bien entendue être développée en ajoutant d'autres ports. Par exemple, vous pouvez vouloir également exposer votre site sur le port HTTPS standard (443). Ceci peut se faire en définissant de nouvelles fermes dédiées à chaque nouveau port que vous souhaitez exposer, et en les associant à leurs frontends correspondants (le premier pour le port standard exposé en production, le second pour le port arbitraire dédié aux développements). +L'infrastructure présentée ici est limitée à un seul port, mais elle peut être étendue en ajoutant d'autres ports. Par exemple, vous pouvez également exposer votre site Web sur le port HTTPS standard (443). Vous pouvez le faire en définissant de nouvelles fermes dédiées à chaque port que vous souhaitez exposer, et en les associant à leurs front-ends correspondants (un pour le port standard exposé en production, le second pour le port arbitraire dédié au développement). -Une autre possibilité pour consolider encore un peu plus votre infrastructure est de multiplier les serveurs attachés à votre (vos) ferme(s). Ceci vous permettra d'ajouter à la simplicité de réalisation de vos déploiements une redondance de vos services (garantissant ainsi leur disponibilité) ainsi qu'une capacité de répartition de charge. +Une autre façon de consolider davantage votre infrastructure est de multiplier les serveurs attachés à vos fermes. De cette façon, vous pouvez rendre vos services plus redondants (garantissant ainsi la disponibilité) et ajouter également une capacité d'équilibrage de charge. ## Aller plus loin -Échangez avec notre [communauté d'utilisateurs](/links/community). +Échangez avec notre [communauté d'utilisateurs](/links/community). \ No newline at end of file From 07b2f58a9acfb476fa11bdba3cd9c34a19a4844a Mon Sep 17 00:00:00 2001 From: Slimane ALI Date: Fri, 17 Oct 2025 02:23:28 +0200 Subject: [PATCH 03/23] SMTP update + dates Updated the SMTP guides to use a more professional tone across the document. --- .../case_blue_green/guide.en-gb.md | 2 +- .../case_blue_green/guide.fr-fr.md | 4 +- .../load_balancer/case_smtp/guide.en-gb.md | 103 +++++++++--------- .../load_balancer/case_smtp/guide.fr-fr.md | 70 ++++++------ 4 files changed, 85 insertions(+), 94 deletions(-) diff --git a/pages/network/load_balancer/case_blue_green/guide.en-gb.md b/pages/network/load_balancer/case_blue_green/guide.en-gb.md index d5ee4f7a18b..126d8836804 100644 --- a/pages/network/load_balancer/case_blue_green/guide.en-gb.md +++ b/pages/network/load_balancer/case_blue_green/guide.en-gb.md @@ -1,7 +1,7 @@ --- title: 'Deploying a blue-green infrastructure' excerpt: 'This guide will show you how to deploy a blue-green infrastructure with the OVHcloud Load Balancer' -updated: 2019-02-25 +updated: 2025-10-17 --- ## Objective diff --git a/pages/network/load_balancer/case_blue_green/guide.fr-fr.md b/pages/network/load_balancer/case_blue_green/guide.fr-fr.md index 3f87ee3fc8e..6c365817ac6 100644 --- a/pages/network/load_balancer/case_blue_green/guide.fr-fr.md +++ b/pages/network/load_balancer/case_blue_green/guide.fr-fr.md @@ -1,14 +1,14 @@ --- title: "Déploiement d'une infrastructure blue-green" excerpt: "Ce guide vous montre comment déployer une infrastructure blue-green avec le Load Balancer OVHcloud" -updated: 2019-02-25 +updated: 2025-10-17 --- ## Objectif Ce guide présente un cas d'usage spécifique du service Load Balancer OVHcloud : la configuration d'un service visant à faciliter le basculement fluide du trafic entre l'environnement de production et un nouvel environnement candidat à la production, également appelé infrastructure `blue-green`{.action}. -Une infrastructure `blue-green`{.action} vous permet d'éviter toute interruption de service de votre infrastructure. Le principal avantage de ce type de déploiement est de pouvoir préparer des mises à jour et/ou des opérations de maintenance dans un environnement isolé de votre environnement de production. Vous pouvez ainsi tester vos modifications avant la mise en production, les annuler rapidement en cas de détection de défaillances, et ce, avec une interruption de service quasi nulle. +Une infrastructure `blue-green`{.action} vous permet d'éviter toute interruption de service de votre infrastructure. Le principal avantage de ce type de déploiement est de pouvoir préparer des mises à jour et/ou des opérations de maintenance dans un environnement isolé de votre environnement de production. Vous pouvez ainsi tester vos modifications avant la mise en production, les annuler rapidement en cas de défaillance, et ce, avec une interruption de service quasi nulle. **Ce guide vous montre comment déployer une infrastructure blue-green avec le Load Balancer OVHcloud.** diff --git a/pages/network/load_balancer/case_smtp/guide.en-gb.md b/pages/network/load_balancer/case_smtp/guide.en-gb.md index 148b5f7fe61..b8553019049 100644 --- a/pages/network/load_balancer/case_smtp/guide.en-gb.md +++ b/pages/network/load_balancer/case_smtp/guide.en-gb.md @@ -1,40 +1,36 @@ --- -title: 'Configuring SMTP on a Load Balancer service' -excerpt: 'Find out how to use SMTP with the OVH Load Balancer' -updated: 2018-12-28 +title: 'How to configure SMTP on a Load Balancer service' +excerpt: 'Find out how to use SMTP with the OVHcloud Load Balancer' +updated: 2025-10-17 --- ## Objective -In this guide, we will configure a basic TCP load balancing service, for one or more SMTP servers. A TCP front-end will listen to TCP traffic on port 25. It is configured to direct traffic to a TCP farm with one or more TCP servers, depending on how you choose to configure it. +**This guide outlines how to configure the OVHcloud Load Balancer to distribute traffic across multiple SMTP servers.** -**This guide is designed to help you configure an OVH Load Balancer service in order to balance load across several servers that respond in SMTP.** +## Requirements -> [!warning] -> -> Questions on what an SMTP service is and how it works will not be covered here. This guide is aimed at readers who have a general understanding of SMTP, or practical experience with it. -> +- An [OVHcloud Load balancer](/links/network/load-balancer) service in your OVHcloud account. +- Access to the [OVHcloud Control Panel](/links/manager). +- A Postfix-type SMTP service installed and configured on your servers. -> [!warning] -> -> We will assume that you already have a Postfix SMTP service set up and configured your servers. -> +## Instructions > [!warning] > -> This guide will take you through the steps required. Depending on the way you have designed your architecture, some configurations may vary. +> This guide assumes a working knowledge of SMTP protocol and service operation. > -As a reminder, each protocol (HTTP, TCP and UDP) in the OVH Load Balancer service has its own associated front-ends, farms and servers. +As a reminder, each protocol (HTTP, TCP and UDP) in the OVHcloud Load Balancer service has its own associated front-ends, farms and servers. > [!warning] > -> The order in which elements are created is important. In particular, the server farms must be configured before we can attach servers to them. +> The order in which elements are created is important. In particular, the server farms must be configured before servers can be attached to them. > -In the Sunrise Control Panel, you will see the features detailed below: +In the Control Panel, you will see the features detailed below: -![OVH Load Balancer service](images/iplb_service.png){.thumbnail} +![OVHcloud Load Balancer service](images/iplb_service.png){.thumbnail} Via the OVH API, in the section: @@ -43,29 +39,29 @@ Via the OVH API, in the section: > @api {v1} /ipLoadbalancing GET /ipLoadbalancing > -For more information on the API’s features, you can refer to [the following guide in French](/pages/network/load_balancer/use_api_reference). +For more information on the API features, you can refer to [the following guide](/pages/network/load_balancer/use_api_reference). -## Add a server farm. +### Add a server farm -We will add a farm of TCP servers to our service, which is the part that balances traffic on the servers. +A farm of TCP servers must be added to the service; this component manages traffic balancing across the servers. -### Via the Sunrise Control Panel. +#### Via the Control Panel In the `Farms`{.action} tab for servers, click on the `+TCP/TLS`{.action} button. -Fill in the fields. The mandatory fields for a basic configuration are *Port* and *Zone*. In our case, for SMTP, port 25 is used. If no ports are specified, your OVH Load Balancer will automatically use the same port as the corresponding front-end. +Fill in the fields. The mandatory fields for a basic configuration are *Port* and *Zone*. For SMTP, port 25 is used. If no ports are specified, your OVHcloud Load Balancer will automatically use the same port as the corresponding front-end. -As an option, you can add an SMTP probe on your farm. +Optionally, you can add an SMTP probe on your farm. ![Add a server farm via the Control Panel](images/add_farm.png){.thumbnail} -Click `Add`{.action} once you have filled in the fields. +Click `Add`{.action} once the fields are filled. Your server farm should appear in the list, in the `Farms`{.action} tab. ![Details of the server farm created](images/resume_farm.png){.thumbnail} -### Via the API +#### Via the API - List of TCP server farms: @@ -102,30 +98,30 @@ Your server farm should appear in the list, in the `Farms`{.action} tab. > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/tcp/farm/{farmId} > -## Add a server. +### Add a server -We will now add a server to our server farm. +A server must now be added to the server farm. -### Via the Sunrise Control Panel. +#### Via the Control Panel -In the `Farms`{.action} tab, select the farm you want to add a server to by clicking on the corresponding line. The list of servers already configured in the farm will appear beneath the list of farms, along with the `Add a server`{.action} button. Click on this button to add a new server. +In the `Farms`{.action} tab, select the farm you want to add a server to by clicking on the corresponding line. The list of servers already configured in the farm will appear beneath the list of farms, along with the `Add a server`{.action} button. Click this button to add a new server. -Only the *IPv4 address*, *Status* and *ProxyProtocol version* fields are mandatory. If a server does not use the same port as the one defined earlier in the farm, you may overload it by configuring a server. However, to keep the configuration as standard as possible and easy to maintain, we recommend only using this parameter in advanced cases. +The mandatory fields are the *IPv4 address*, *Status*, and *ProxyProtocol version*. If a server port is configured, it will override the port defined in the farm. To keep the configuration as standard as possible and easy to maintain, we recommend only using this parameter in advanced cases. > [!warning] > -> It is important to configure ProxyProtocol in version v1, so that you can get the real source IP on your SMTP service. Postfix is compatible with this protocol. +> It is important to configure ProxyProtocol in version v1 so that you can retrieve the real source IP on your SMTP service. Postfix is compatible with this protocol. > ![Add a server to a farm.](images/add_server.png){.thumbnail} -Click `Add`{.action} once you have filled in the fields. +Click `Add`{.action} once the fields are filled. Your server should appear in the server list, in the `Farms`{.action} tab, just below the list of farms. ![Details of the server created.](images/resume_server.png){.thumbnail} -### Via the API +#### Via the API - List of servers in the farm: @@ -162,29 +158,29 @@ Your server should appear in the server list, in the `Farms`{.action} tab, just > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/tcp/farm/{farmId}/server > -## Add a front-end +### Add a front-end -We will now add a `front-end`{.action} to our service, and connect it to our server farm. The front-end is the part of your OVH Load Balancer that exposes your service on the internet. +A `front-end`{.action} must now be added to the service and connected to the server farm. The front-end is the component of your OVHcloud Load Balancer that exposes your service to the internet. -### Via the Sunrise Control Panel. +#### Via the Control Panel Go to the `+ Front-ends`{.action} tab, and click `+TCP/TLS`{.action}. -Fill in the fields. The only mandatory fields for a basic configuration are *Port* (25 for a standard SMTP service), *Zone* and *Probe*, if you configured a probe on your farm. If you want your service to be available across several ports at once, you can specify a list of ports, separated by commas, or a range of ports, in the format "start_port-end_port". +Fill in the fields. The mandatory fields for a basic configuration are *Port* (25 for a standard SMTP service), *Zone* and *Probe* (if a probe was configured on your farm). If you want your service to be available across several ports at once, you can specify a list of ports, separated by commas, or a port range, in the format "start_port-end_port". -If you have routed Additional IPs to your OVH Load Balancer service, you can also attach a front-end to one or more specific Additional IPs. +If you have routed Additional IPs to your OVHcloud Load Balancer service, you can also attach a front-end to one or more specific Additional IPs. -Please remember to specify the farm you created earlier as a “default farm”. +Ensure the farm you created earlier is specified as the “default farm”. ![Add a front-end](images/add_frontend.png){.thumbnail} -Click `Add`{.action} once you have filled in the fields. +Click `Add`{.action} once the fields are filled. Your front-end must appear in the list, in the `Front-ends`{.action} tab. ![Details of the front-end created](images/resume_frontend.png){.thumbnail} -### Via the API +#### Via the API - List of TCP front-ends: @@ -221,17 +217,17 @@ Your front-end must appear in the list, in the `Front-ends`{.action} tab. > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/tcp/frontend/{frontendId} > -## Apply the modifications +### Apply the modifications -The modifications made to your OVH Load Balancer must be *explicitly applied* in each of the zones configured for your service. Only at this point will they be visible to your website visitors. This way, you can make complex configuration changes several times, and only apply them once the configuration is ready. +Modifications made to your OVHcloud Load Balancer must be *explicitly applied* in each of the zones configured for your service. They will only become visible to your users at this point. This process allows for complex configuration changes to be prepared and applied only when fully ready. -If you have several zones, you must apply the same configuration for each of them. +If you have several zones, the same configuration must be applied to each. -### Via the Sunrise Control Panel. +#### Via the Control Panel -Go the homepage for the OVH Load Balancer, and click `Apply:Zone`{.action} for each of the zones concerned. +Go to the homepage for the OVHcloud Load Balancer, and click `Apply:Zone`{.action} for each of the zones concerned. -### Via the API. +#### Via the API - Refresh a zone: @@ -240,21 +236,20 @@ Go the homepage for the OVH Load Balancer, and click `Apply:Zone`{.action} for e > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh > -## Postfix configuration. +### Postfix configuration To make Postfix compatible with HAProxy *ProxyProtocol*, an option is required in the postfix main.cf configuration file: **smtp_upstream_proxy_protocol = haproxy** -You then need to restart your Postfix daemon. +The Postfix daemon must then be restarted. -## Confirmation. +### Confirmation -After you have completed all of these steps, you should now have a functional Load Balancer service for your SMTP servers. You can now check the service status by requesting your IP Load Balancer as an SMTP server. +Upon completing these steps, you will have a functional Load Balancer service for your SMTP servers. The service status can now be checked by requesting your IP Load Balancer as an SMTP server. ![Connection to SMTP via telnet](images/resume_validate.png){.thumbnail} ## Go further -Join our community of users on . - +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/case_smtp/guide.fr-fr.md b/pages/network/load_balancer/case_smtp/guide.fr-fr.md index 4eb8216605a..c9a59943e17 100644 --- a/pages/network/load_balancer/case_smtp/guide.fr-fr.md +++ b/pages/network/load_balancer/case_smtp/guide.fr-fr.md @@ -1,33 +1,29 @@ --- -title: 'Configuration SMTP sur un service Load Balancer' -excerpt: 'Cas pratique SMTP' -updated: 2018-12-28 +title: 'Comment configurer le SMTP sur un service Load Balancer' +excerpt: 'Découvrez comment utiliser le SMTP avec le Load Balancer OVHcloud' +updated: 2025-10-17 --- ## Objectif -Ce guide a pour but de vous aider à configurer un service OVHcloud Load Balancer pour répartir la charge sur plusieurs serveurs répondant convenablement en SMTP. +**Ce guide détaille la configuration du Load Balancer OVHcloud afin de distribuer le trafic entre plusieurs serveurs SMTP.** ## Prérequis - Posséder une offre [OVHcloud Load balancer](/links/network/load-balancer) dans votre compte OVHcloud. - Être connecté à votre [espace client OVHcloud](/links/manager). -- Posséder un service SMTP de type postfix installé et configuré sur vos serveurs +- Posséder un service SMTP de type Postfix installé et configuré sur vos serveurs. ## En pratique > [!warning] > -> La définition d'un service SMTP et son fonctionnement sont des notions qui ne seront pas abordées ici. -> Il est considéré ici que ces informations sont raisonnablement comprises et/ou maîtrisées. +> Ce guide présuppose une connaissance fonctionnelle du protocole SMTP et de son service. > -> Nous allons vous guider au travers des différentes étapes. -> Dépendant de vos choix d'architecture, certaines configurations peuvent différer. -> -Dans ce guide, nous allons configurer un service simple de Load Balancing TCP, pour un (ou plusieurs) serveur(s) SMTP. Un frontend TCP écoutera le trafic TCP sur le port 25. Il sera configuré pour diriger le trafic sur une ferme TCP, avec un ou plusieurs serveurs TCP, selon votre configuration. +Dans ce guide, nous configurons un service simple d'équilibrage de charge TCP pour un (ou plusieurs) serveur(s) SMTP. Un *frontend* TCP écoutera le trafic TCP sur le port 25. Il sera configuré pour diriger le trafic vers une ferme TCP, comprenant un ou plusieurs serveurs TCP, selon la configuration retenue. -Pour rappel, chaque protocole (HTTP, TCP et UDP) dans le service OVHcloud Load Balancer dispose de ses propres frontends, fermes et serveurs associés. +Pour rappel, chaque protocole (HTTP, TCP et UDP) du service OVHcloud Load Balancer dispose de ses propres *frontends*, fermes et serveurs associés. > [!warning] > @@ -35,7 +31,7 @@ Pour rappel, chaque protocole (HTTP, TCP et UDP) dans le service OVHcloud Load B > En particulier, les fermes de serveurs doivent être configurées **avant** de pouvoir leur attacher des serveurs. > -Dans l'espace client OVHcloud, nous allons retrouver les fonctionnalités détaillées ci-dessous : +Les fonctionnalités détaillées ci-dessous sont disponibles dans l'espace client OVHcloud : ![Service OVHcloud Load Balancer](images/iplb_service.png){.thumbnail} @@ -50,22 +46,22 @@ Pour plus d'informations sur les fonctionnalités de l'API, consultez la page « ### Ajouter une ferme de serveurs -Nous allons ajouter une ferme de serveurs TCP à notre service, c'est à dire la partie en charge de répartir le trafic sur les serveurs. +Une ferme de serveurs TCP doit être ajoutée à notre service ; ce composant est en charge de la répartition du trafic sur les serveurs. #### Depuis l'espace client OVHcloud Dans l'onglet `Fermes`{.action} de serveurs, cliquez sur le bouton `+TCP/TLS`{.action}. -Remplissez les différents champs. Les champs obligatoires pour une configuration simple sont le *Port* et la *Zone*. Dans notre cas, pour SMTP, le port utilisé est le port 25. Si aucun port n'est spécifié, votre OVHcloud Load Balancer utilisera automatiquement le même port que le frontend correspondant. - -![Ajout d'une ferme de serveurs via le Manager](images/add_farm.png){.thumbnail} - -Cliquez sur le bouton `Ajouter`{.action} une fois les champs remplis. +Remplissez les différents champs. Les champs obligatoires pour une configuration simple sont le *Port* et la *Zone*. Dans notre cas, pour SMTP, le port utilisé est le port 25. Si aucun port n'est spécifié, votre OVHcloud Load Balancer utilisera automatiquement le même port que le *frontend* correspondant. Vous pouvez optionnelement ajouter une sonde de type SMTP sur votre ferme. +![Ajout d'une ferme de serveurs via le Manager](images/add_farm.png){.thumbnail} + ![Ajout d'une ferme de serveurs via le Manager](images/add_farm_Probe.png){.thumbnail} +Cliquez sur le bouton `Ajouter`{.action} une fois les champs remplis. + Votre ferme de serveurs devrait apparaître dans la liste, sous l'onglet `Fermes`{.action}. ![Détails de la ferme de serveurs créée](images/resume_farm.png){.thumbnail} @@ -109,17 +105,17 @@ Votre ferme de serveurs devrait apparaître dans la liste, sous l'onglet `Fermes ### Ajouter un serveur -Nous allons maintenant ajouter un serveur à notre ferme de serveurs. +Un serveur doit maintenant être ajouté à la ferme de serveurs. #### Depuis l'espace client OVHcloud Toujours dans l'onglet `Fermes`{.action}, sélectionnez la ferme dans laquelle vous souhaitez ajouter un serveur en cliquant sur la ligne correspondante. La liste des serveurs déjà configurés dans la ferme apparaît en dessous de la liste des fermes, ainsi qu'un bouton `+Server`{.action}. Cliquez sur ce bouton pour ajouter un nouveau serveur. -Seuls les champs *Adresse IPv4*, *État* et *Version du ProxyProtocol* sont obligatoires. Si un serveur n'utilise pas le même port que celui défini plus haut dans la ferme, il est possible de le surcharger dans la configuration du serveur. Cependant, afin de conserver une configuration la plus homogène et maintenable possible, il est recommandé de n'utiliser ce paramètre que dans les cas avancés. +Les champs obligatoires sont l'*Adresse IPv4*, l'*État* et la *Version du ProxyProtocol*. Si un port de serveur est configuré, il remplacera le port défini au niveau de la ferme. Afin de conserver une configuration la plus homogène et maintenable possible, il est recommandé de n'utiliser ce paramètre que dans les cas avancés. > [!warning] > -> Il est important de configurer le ProxyProtocol en version v1, afin d'obtenir l'IP source réelle sur votre service SMTP. +> Il est important de configurer le ProxyProtocol en version v1 afin d'obtenir l'IP source réelle sur votre service SMTP. > Postfix est compatible avec ce protocole. > @@ -171,57 +167,57 @@ Votre serveur devrait apparaître dans la liste des serveurs dans l'onglet `Ferm ### Ajouter un frontend -Nous allons maintenant ajouter un frontend à notre service et le connecter à notre ferme de serveurs. Le frontend est la partie de votre OVHcloud Load Balancer qui sert à exposer votre service sur Internet. +Un *frontend* doit maintenant être ajouté à notre service et connecté à la ferme de serveurs. Le *frontend* est le composant de votre OVHcloud Load Balancer qui expose votre service sur Internet. #### Depuis l'espace client OVHcloud Dans l'onglet `+Frontends`{.action}, cliquez sur le bouton `+TCP/TLS`{.action}. -Remplissez les différents champs. Les seuls champs obligatoires pour une configuration simple sont le *Port* (25 pour un service SMTP standard), la *Zone* et la *Sonde* si vous en avez configuré une dans votre Ferme. Si vous souhaitez que votre service soit disponible sur plusieurs ports en même temps, vous pouvez spécifier une liste de ports séparés par des virgules ou une plage de ports de la forme "-". +Remplissez les différents champs. Les seuls champs obligatoires pour une configuration simple sont le *Port* (25 pour un service SMTP standard), la *Zone* et la *Sonde* (si vous en avez configuré une dans votre Ferme). Si vous souhaitez que votre service soit disponible sur plusieurs ports en même temps, vous pouvez spécifier une liste de ports séparés par des virgules ou une plage de ports de la forme "-". -Si vous avez routé des Additional IP vers votre service OVHcloud Load Balancer, vous pouvez également attacher un frontend à une ou plusieurs Additional IP spécifiques. +Si vous avez routé des Additional IP vers votre service OVHcloud Load Balancer, vous pouvez également attacher un *frontend* à une ou plusieurs Additional IP spécifiques. -N'oubliez pas de spécifier comme « Ferme par défaut » la ferme créée précédemment. +Assurez-vous de spécifier la ferme créée précédemment comme « Ferme par défaut ». ![Ajout d'un frontend](images/add_frontend.png){.thumbnail} Cliquez sur le bouton `Ajouter`{.action} une fois les champs remplis. -Votre frontend devrait apparaître dans la liste, sous l'onglet `Frontends`{.action}. +Votre *frontend* devrait apparaître dans la liste, sous l'onglet `Frontends`{.action}. ![Détails du frontend créé](images/resume_frontend.png){.thumbnail} #### Depuis l'API OVHcloud -- Liste des frontends TCP : +- Liste des *frontends* TCP : > [!api] > > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/tcp/frontend > -- Détails d'un frontend spécifique : +- Détails d'un *frontend* spécifique : > [!api] > > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/tcp/frontend/{frontendId} > -- Ajout d'un nouveau frontend : +- Ajout d'un nouveau *frontend* : > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/tcp/frontend > -- Modification d'un frontend spécifique : +- Modification d'un *frontend* spécifique : > [!api] > > @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/tcp/frontend/{frontendId} > -- Suppression d'un frontend spécifique : +- Suppression d'un *frontend* spécifique : > [!api] > @@ -230,9 +226,9 @@ Votre frontend devrait apparaître dans la liste, sous l'onglet `Frontends`{.act ### Appliquer les modifications -Les modifications apportées à votre service OVHcloud Load Balancer doivent être *appliquées explicitement* dans chacune des zones configurées pour votre service OVHcloud Load Balancer. C'est seulement à ce moment qu'elles seront visibles pour vos visiteurs. Cela permet de faire un changement complexe de configuration en plusieurs fois, et de ne l'appliquer que lorsque la configuration est prête. +Les modifications apportées à votre service OVHcloud Load Balancer doivent être *appliquées explicitement* dans chacune des zones configurées pour votre service. C'est seulement à ce moment qu'elles deviendront visibles pour vos visiteurs. Ce processus permet de préparer des changements de configuration complexes et de ne les appliquer qu'une fois la configuration entièrement prête. -Si vous avez plusieurs zones, vous devrez appliquer la même configuration pour chacune de vos zones. +Si vous avez plusieurs zones, la même configuration devra être appliquée pour chacune de vos zones. #### Depuis l'espace client OVHcloud @@ -247,15 +243,15 @@ Rendez-vous sur la page principale de votre service OVHcloud Load Balancer et cl > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh > -### Configuration de postfix +### Configuration de Postfix -Afin de rendre postfix compatible avec le *ProxyProtocol* de haproxy, une option est requise dans le fichier de configuration `postfix main.cf`. +Afin de rendre Postfix compatible avec le *ProxyProtocol* de HAProxy, une option est requise dans le fichier de configuration `postfix main.cf` : ```bash smtp_upstream_proxy_protocol = haproxy ``` -Vous devez ensuite redémarrer votre démon postfix. +Le daemon Postfix doit ensuite être redémarré. ### Validation From ba51681bdd4a0162dddedc2cf6a5b2079230fd7c Mon Sep 17 00:00:00 2001 From: Slimane ALI Date: Fri, 17 Oct 2025 02:34:13 +0200 Subject: [PATCH 04/23] create_balancing update Updated the load balancing methods guides to use a more professional tone across the document. --- .../create_balancing/guide.en-gb.md | 55 ++++++++++--------- .../create_balancing/guide.fr-fr.md | 54 +++++++++--------- 2 files changed, 55 insertions(+), 54 deletions(-) diff --git a/pages/network/load_balancer/create_balancing/guide.en-gb.md b/pages/network/load_balancer/create_balancing/guide.en-gb.md index 0d25c0f0aea..63331c2c3ff 100644 --- a/pages/network/load_balancer/create_balancing/guide.en-gb.md +++ b/pages/network/load_balancer/create_balancing/guide.en-gb.md @@ -1,57 +1,58 @@ --- title: Load balancing methods -excerpt: Find out about the various load balancing methods used by the OVH Load Balancer -updated: 2018-01-17 +excerpt: Discover the various load balancing algorithms available with the OVHcloud Load Balancer +updated: 2025-10-17 --- ## Objective -The new OVH Load Balancer service offers a variety of load balancing methods for your services. This process determines the way in which the OVH Load Balancer distributes the requests received by your servers. +The OVHcloud Load Balancer service supports a variety of load balancing algorithms for your services. This setting dictates how the Load Balancer distributes incoming client requests among the servers in a farm. -**This guide will provide an introduction to the various load balancing methods, and will explain how you can modify them.** +**This guide introduces the various load balancing methods and explains how to modify them.** ## Requirements -- You must be logged in to the [OVH Control Panel](/links/manager). +- An [OVHcloud Load Balancer](/links/network/load-balancer) service in your OVHcloud account. +- Access to the [OVHcloud Control Panel](/links/manager). - You need to have created a server farm. ## Instructions -### Different load balancing methods +### Available Load Balancing Algorithms -Load balancing is used in server farms. This setting defines the way that requests are distributed between the servers within the farm. +The load balancing setting is applied at the server farm level and defines the method by which client requests are distributed among the servers within that farm. -To understand the basics of the OVH Load Balancer service, please refer to the [Load Balancer Introduction](/pages/network/load_balancer/use_presentation). +For an overview of the OVHcloud Load Balancer service components, please refer to the [Load Balancer Introduction](/pages/network/load_balancer/use_presentation). |Algorithm|Features| |---|---| -|First|The first available server receives the connection. The server is chosen according to its ID, from smallest to largest.| -|LeastConn|Selects the server that has the lowest number of active connections. This setting is recommended for long sessions, with low levels of traffic. The *RoundRobin* algorithm is applied to groups of servers that have the same number of active connections.| -|RoundRobin|Selects the servers one after the other for each connection. **This is the default algorithm.**| -|Source|This algorithm *hashes* the source IP address, then divides the result by the number of servers currently running. The same source IP address will then still be redirected to the same server, provided that it continues to run.| -|URI|This algorithm *hashes* part or all of the URI, then divides the result by the number of servers currently running. The same URI will then still be redirected to the same server, provided that it continues to run.| +|**First**|Directs the connection to the first available server based on its ID (smallest to largest).| +|**LeastConn**|Selects the server with the lowest number of active connections. This is recommended for long-duration sessions with light traffic. The *RoundRobin* algorithm is used for tie-breaking among equally loaded servers.| +|**RoundRobin**|Distributes connections sequentially, one after the other, for each new request. **This is the default algorithm.**| +|**Source**|Uses a hash of the source IP address to consistently redirect the same client IP to the same server, provided the server remains operational.| +|**URI**|Uses a hash of part or all of the URI path to consistently redirect identical URIs to the same server, provided the server remains operational. *(Applicable to HTTP/HTTPS farms only.)*| ### Modify a server farm’s load balancing method via the Control Panel -- In the `Server farms`{.action} section (1), you will see the farms that have been created. You can edit them by clicking the three dots on the right-hand side (2), then `Change`{.action}: +- In the `Server farms`{.action} section (1), locate the desired farm. You can edit it by clicking the three dots on the right-hand side (2), then `Change`{.action}: ![Modify a farm](images/server_cluster_change.png){.thumbnail} -In `Advanced settings`{.action}, you can modify your `Load balancing method`{.action}: +In `Advanced settings`{.action}, modify the `Load balancing method`{.action}: ![Modify a farm](images/distrib_mode_edit.png){.thumbnail} -Once you have selected your preferred load balancing method, click `Update`{.action}, then `Apply configuration`{.action} in the yellow banner that appears: +Once your preferred method is selected, click `Update`{.action}, then click `Apply configuration`{.action} in the yellow banner that appears: ![Apply configuration](images/apply_config.png){.thumbnail} ### Modify a server farm’s load balancing method via the API -You can modify the load balancing method settings by editing them in the server farm. +The load balancing method is changed by updating the corresponding field within the server farm configuration. -- View details on a server farm +#### View details on a server farm -With this call instruction, you can view details on a server farm if you know its ID. In this example, we will work on an HTTP farm: +Use this call to view the details of a server farm given its ID. In this example, we work with an HTTP farm: > [!api] > @@ -60,22 +61,22 @@ With this call instruction, you can view details on a server farm if you know it |Setting|Meaning| |---|---| -|ServiceName*|Your Load Balancer service ID| +|serviceName*|Your Load Balancer service ID| |farmId*|The farm’s ID number| |Response (BackendHttp)|Meaning| |---|---| |farmId|The farm’s ID number| -|balance|Balance type currently set for the farm| +|balance|The load balancing algorithm currently set for the farm| |zone|Name of the zone in which the farm is configured| |port|Port used to contact the servers configured on the farm| |probe|Type of probe currently configured on the farm| |displayName|Name given to this farm| |stickiness|Connection monitoring method currently set for the farm| -- Modify a server farm’s load balancing method +#### Modify a server farm’s load balancing method -With this call instruction, you can edit the settings of a server farm if you know its ID. In this example, we will work on an HTTP farm. To modify the balancing method, the `BackendHttp.balance` field must be updated with an available balancing method: +Use this call to edit the settings of a server farm given its ID. In this example, we work with an HTTP farm. To modify the balancing method, update the `BackendHttp.balance` field with an available algorithm: > [!api] > @@ -84,11 +85,11 @@ With this call instruction, you can edit the settings of a server farm if you kn |Setting|Meaning| |---|---| -|ServiceName*|Your Load Balancer service ID| +|serviceName*|Your Load Balancer service ID| |farmId*|The farm’s ID number| |BackendHttp.balance|Preferred balancing method for this farm| -- Apply the modifications +#### Apply the modifications > [!api] > @@ -97,9 +98,9 @@ With this call instruction, you can edit the settings of a server farm if you kn |Setting|Meaning| |---|---| -|ServiceName*|Your Load Balancer service ID| +|serviceName*|Your Load Balancer service ID| |zone*|Name of the zone in which to deploy the configuration| ## Go further -Join our community of users on . +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/create_balancing/guide.fr-fr.md b/pages/network/load_balancer/create_balancing/guide.fr-fr.md index 5ba2fa28b7f..492f2203216 100644 --- a/pages/network/load_balancer/create_balancing/guide.fr-fr.md +++ b/pages/network/load_balancer/create_balancing/guide.fr-fr.md @@ -1,14 +1,14 @@ --- -title: Mode de répartition +title: Modes de répartition excerpt: Découvrez les différents modes de répartition de charge du Load Balancer OVHcloud -updated: 2018-01-17 +updated: 2025-10-17 --- ## Objectif -Le service OVHcloud Load Balancer offre différents types de répartition de charge pour vos services. Ce processus détermine la manière dont le Load Balancer OVHcloud va répartir les requêtes reçues vers vos serveurs. +Le service OVHcloud Load Balancer prend en charge différents algorithmes de répartition de charge pour vos services. Ce paramètre détermine la manière dont le Load Balancer va distribuer les requêtes clientes entrantes vers les serveurs d'une ferme. -**Ce guide vous présente les différents types de répartition de charge et vous explique comment les modifier.** +**Ce guide présente les différents algorithmes de répartition de charge et explique comment les modifier.** ## Prérequis @@ -18,23 +18,23 @@ Le service OVHcloud Load Balancer offre différents types de répartition de cha ## En pratique -### Les différents types de répartition de charge +### Algorithmes de répartition de charge disponibles -La répartition de charge est utilisée dans les fermes de serveurs. C'est ce paramètre qui définit la manière dont les requêtes sont réparties entre les serveurs de la ferme. +L'algorithme de répartition de charge est appliqué au niveau des fermes de serveurs. C'est ce paramètre qui définit la manière dont les requêtes sont réparties entre les serveurs de la ferme. -Pour connaître les différentes parties élémentaires du service OVHcloud Load Balancer, consultez la [présentation du Load Balancer](/pages/network/load_balancer/use_presentation). +Pour une vue d'ensemble des composants du service OVHcloud Load Balancer, consultez la [présentation du Load Balancer](/pages/network/load_balancer/use_presentation). |Algorithme|Fonctionnalités| |---|---| -|First|Le premier serveur disponible reçoit la connexion. Le serveur est choisi en fonction de son ID, du plus petit au plus grand.| -|LeastConn|Sélectionne le serveur qui a le moins de connexions actives, c'est le paramètre recommandé pour de longues sessions avec peu de trafic. L'algorithme *RoundRobin* est appliqué sur les groupes de serveurs qui ont le même nombre de connexion actives.| -|RoundRobin|Sélectionne les serveurs les uns après les autres pour chaque connexion, **c'est l'algorithme par défaut.**| -|Source|Cet algorithme effectue une fonction de *hashage* (hash) sur l'adresse IP source, puis divise le résultat par le nombre de serveurs actuellement actifs. La même adresse IP source sera alors toujours redirigée vers le même serveur, tant que celui-ci reste actif.| -|URI|Cet algorithme effectue une fonction de *hashage* (hash) sur une partie, ou sur l'URI entière, puis divise le résultat par le nombre de serveurs actuellement actifs. La même URI sera alors toujours redirigée vers le même serveur tant que celui-ci reste actif.| +|**First**|Dirige la connexion vers le premier serveur disponible en fonction de son ID (du plus petit au plus grand).| +|**LeastConn**|Sélectionne le serveur qui a le moins de connexions actives. Ceci est recommandé pour les sessions longues avec peu de trafic. L'algorithme *RoundRobin* est appliqué pour départager les serveurs ayant un nombre de connexions actives égal.| +|**RoundRobin**|Distribue les connexions séquentiellement, les unes après les autres, pour chaque nouvelle requête. **C'est l'algorithme par défaut.**| +|**Source**|Utilise une fonction de *hachage* sur l'adresse IP source pour rediriger systématiquement la même IP cliente vers le même serveur, tant que celui-ci reste opérationnel.| +|**URI**|Utilise une fonction de *hachage* sur une partie ou la totalité de l'URI pour rediriger systématiquement les URI identiques vers le même serveur, tant que celui-ci reste opérationnel. *(Applicable uniquement aux fermes HTTP/HTTPS.)*| -### Modifier le mode de répartition de charge d'une ferme via l'espace client +### Modifier l'algorithme de répartition de charge d'une ferme via l'espace client -Dans la section `Fermes de serveur`{.action} vous verrez les fermes actuellement créées. Il vous suffit d'éditer l'une d'entre elles en cliquant sur les trois points à droite puis `Modifier`{.action} : +Dans la section `Fermes de serveur`{.action}, vous verrez les fermes actuellement créées. Il vous suffit d'éditer l'une d'entre elles en cliquant sur les trois points à droite puis `Modifier`{.action} : ![Modification d'une ferme](images/server_cluster_change.png){.thumbnail} @@ -42,17 +42,17 @@ Dans les `Paramètres avancés`{.action} vous pourrez modifier votre `Mode de r ![Modification d'une ferme](images/distrib_mode_edit.png){.thumbnail} -Une fois le mode de répartition souhaité sélectionné, cliquez sur `Mettre à jour`{.action}, puis sur `Appliquer la configuration`{.action} dans le bandeau jaune qui apparaît : +Une fois l'algorithme souhaité sélectionné, cliquez sur `Mettre à jour`{.action}, puis sur `Appliquer la configuration`{.action} dans le bandeau jaune qui apparaît : ![Appliquer la configuration](images/apply_config.png){.thumbnail} -### Modifier le mode de répartition de charge d'une ferme depuis l'API OVHcloud +### Modifier l'algorithme de répartition de charge d'une ferme depuis l'API OVHcloud -La modification des paramètres de mode de répartition s'effectue en éditant ceux de la ferme de serveurs. +La modification de l'algorithme de répartition s'effectue en éditant le champ correspondant dans la configuration de la ferme de serveurs. #### Voir le détail d'une ferme -Cet appel permet de consulter le détail d'une ferme en connaissant son identifiant. Dans cet exemple, nous allons travailler sur une ferme HTTP : +Cet appel permet de consulter le détail d'une ferme en connaissant son identifiant. Dans cet exemple, nous travaillons sur une ferme HTTP : > [!api] > @@ -61,22 +61,22 @@ Cet appel permet de consulter le détail d'une ferme en connaissant son identifi |Paramètre|Signification| |---|---| -|ServiceName\*|Identifiant de votre service Load Balancer| +|serviceName\*|Identifiant de votre service Load Balancer| |farmId\*|Identifiant numérique de la ferme| |Réponse (BackendHttp)|Signification| |---|---| |farmId|Identifiant numérique de la ferme| -|balance|Type de répartition actuellement configuré sur la ferme| +|balance|Algorithme de répartition de charge actuellement configuré sur la ferme| |zone|Nom de la zone où est configurée la ferme| -|port|port utilisé pour contacter les serveurs configurés sur la ferme| +|port|Port utilisé pour contacter les serveurs configurés sur la ferme| |probe|Type de sonde actuellement configurée sur la ferme| |displayName|Nom donné à cette ferme| |stickiness|Mode de suivi de connexion actuellement configuré sur la ferme| -#### Modifier le mode de répartition d'une ferme +#### Modifier l'algorithme de répartition de charge d'une ferme -Cet appel permet de modifier la configuration d'une ferme en connaissant son identifiant. Dans cet exemple, nous allons travailler sur une ferme HTTP. Pour modifier le mode de répartition, le champ `BackendHttp.balance` doit être mis à jour avec un mode de répartition disponible : +Cet appel permet de modifier la configuration d'une ferme en connaissant son identifiant. Dans cet exemple, nous travaillons sur une ferme HTTP. Pour modifier le mode de répartition, le champ `BackendHttp.balance` doit être mis à jour avec un algorithme disponible : > [!api] > @@ -85,9 +85,9 @@ Cet appel permet de modifier la configuration d'une ferme en connaissant son ide |Paramètre|Signification| |---|---| -|ServiceName\*|Identifiant de votre service Load Balancer| +|serviceName\*|Identifiant de votre service Load Balancer| |farmId\*|Identifiant numérique de la ferme| -|BackendHttp.balance|Type de répartition souhaité pour cette ferme| +|BackendHttp.balance|Algorithme de répartition souhaité pour cette ferme| #### Appliquer les modifications @@ -98,9 +98,9 @@ Cet appel permet de modifier la configuration d'une ferme en connaissant son ide |Paramètre|Signification| |---|---| -|ServiceName\*|Identifiant de votre service Load Balancer| +|serviceName\*|Identifiant de votre service Load Balancer| |zone\*|Nom de la zone dans laquelle déployer la configuration| ## Aller plus loin -Échangez avec notre [communauté d'utilisateurs](/links/community). +Échangez avec notre [communauté d'utilisateurs](/links/community). \ No newline at end of file From d5f091ca100b4c3cce58d05f9ae1d545ecd7cf8a Mon Sep 17 00:00:00 2001 From: Slimane ALI Date: Mon, 20 Oct 2025 23:45:31 +0200 Subject: [PATCH 05/23] Requested changes Edited following feedback. --- .../case_blue_green/guide.en-gb.md | 26 ++++++++-------- .../case_blue_green/guide.fr-fr.md | 30 +++++++++---------- .../load_balancer/case_smtp/guide.en-gb.md | 2 +- .../load_balancer/case_smtp/guide.fr-fr.md | 6 ++-- .../order_freecertificate/guide.en-gb.md | 8 ++--- 5 files changed, 36 insertions(+), 36 deletions(-) diff --git a/pages/network/load_balancer/case_blue_green/guide.en-gb.md b/pages/network/load_balancer/case_blue_green/guide.en-gb.md index 126d8836804..7200634a9f7 100644 --- a/pages/network/load_balancer/case_blue_green/guide.en-gb.md +++ b/pages/network/load_balancer/case_blue_green/guide.en-gb.md @@ -6,15 +6,15 @@ updated: 2025-10-17 ## Objective -This guide demonstrates a specific use case for the OVHcloud Load Balancer: the configuration of a service to facilitate seamless traffic switching between production and new production candidate environments, also called a `blue-green`{.action} infrastructure. +This guide demonstrates a specific use case for the OVHcloud Load Balancer: the configuration of a service to facilitate seamless traffic switching between production and new production candidate environments, also called a **blue-green** infrastructure. -With a `blue-green`{.action} infrastructure, you can stop your infrastructure from experiencing any downtime. The main benefit of this deployment type is that you can prepare updates and/or maintenance in an environment that is isolated from your production environment. This way, you can test your changes before they are put into production, undo them quickly if you detect any faults, and do all of this with virtually zero downtime. +With a **blue-green** infrastructure, you can stop your infrastructure from experiencing any downtime. The main benefit of this deployment type is that you can prepare updates and/or maintenance in an environment that is isolated from your production environment. This way, you can test your changes before they are put into production, undo them quickly if you detect any faults, and do all of this with virtually zero downtime. **This guide will show you how to deploy a blue-green infrastructure with the OVHcloud Load Balancer.** ## Requirements -To deploy a `blue-green`{.action} infrastructure, you need the following components: +To deploy a **blue-green** infrastructure, you need the following components: - An OVHcloud [Load Balancer](/links/network/load-balancer) service - Access to the [OVHcloud Control Panel](/links/manager) @@ -28,9 +28,9 @@ You have an infrastructure designed to host your live website. This environment hosts the website’s code, in addition to all essential applications (web servers, database servers, etc.). You need to update your applications and/or your code on a regular basis. You want to be able to test your updates without impacting the website's availability or functionality for end-users. -One way to achieve this is by deploying a `blue-green`{.action} infrastructure. +One way to achieve this is by deploying a **blue-green** infrastructure. -The principle of a `blue-green`{.action} deployment involves being able to switch easily from a development infrastructure to a production infrastructure, and vice versa. This switch must be done in a way that is transparent for your users. To do this, public traffic will be routed to the standard HTTP port 80 for access to the production infrastructure, and a non-standard port, such as 8888, will be used to access the development infrastructure. +The principle of a **blue-green** deployment involves being able to switch easily from a development infrastructure to a production infrastructure, and vice versa. This switch must be done in a way that is transparent for your users. To do this, public traffic will be routed to the standard HTTP port 80 for access to the production infrastructure, and a non-standard port, such as 8888, will be used to access the development infrastructure. ## Deploy the infrastructures @@ -40,7 +40,7 @@ The production infrastructure can be accessed by your customers on the standard During the initial setup phase, roles are provisionally assigned to each infrastructure component. `Infrastructure A`{.action} serves as the initial production environment, while `infrastructure B`{.action} serves as the staging environment. At this stage, we will consider them to be similar to one another. -A `blue-green`{.action} infrastructure involves switching from infrastructure A to infrastructure B, once infrastructure B has been fully updated and validated. The Load Balancer will manage this switch. +A **blue-green** infrastructure involves switching from infrastructure A to infrastructure B, once infrastructure B has been fully updated and validated. The Load Balancer will manage this switch. The diagram below gives a general idea of the architecture: @@ -52,7 +52,7 @@ This infrastructure is made up of a server farm that will later be associated wi In our scenario, we will declare a farm of servers for the HTTP service. Please note that you can create as many farms (as well as TCP and/or UDP services) as are required for your final service to be exposed to your customers. -#### Via the OVH Control Panel: +#### Via the OVHcloud Control Panel: ![Add a new HTTP farm dedicated to infrastructure A](images/ferme1.png){.thumbnail} @@ -86,7 +86,7 @@ With the additional calls listed below, you can list, modify and delete your ser Associate a server with your farm, if it is a physical server hosting your production infrastructure. The service exposed to the front-end is supplied by the server’s port 8080. Please note that you can associate one or more servers with each farm (to balance the load and/or offer higher fault tolerance, for ex.). -#### Via the OVH Control Panel: +#### Via the OVHcloud Control Panel: ![Add a new server to the farm HTTP A](images/serveur1.png){.thumbnail} @@ -149,7 +149,7 @@ Deploy the server farm for the HTTP service (and/or any other TCP or UDP service Associate a server with your farm. Here, it involves one or more physical servers hosting your development infrastructure. -#### Via the OVH Control Panel: +#### Via the OVHcloud Control Panel: ![Add a new server to the farm HTTP B](images/serveur2.png){.thumbnail} @@ -176,7 +176,7 @@ At this stage, here is the configuration status for your two farms: ## Front-ends -The magic of `blue-green`{.action} deployment lies in the configuration of your front-ends. At this stage, we have configure two functionally identical infrastructures. For both infrastructures, you have declared one or more server farms, each with their own set of associated servers. +The magic of **blue-green** deployment lies in the configuration of your front-ends. At this stage, we have configure two functionally identical infrastructures. For both infrastructures, you have declared one or more server farms, each with their own set of associated servers. To switch simply from one infrastructure to another, we will use front-ends. @@ -190,7 +190,7 @@ To do this, we need to declare two front-ends. The first one will give you acces ### Blue front-end This `front-end`{.action} is dedicated to accessing the production infrastructure. The ports exposed to your customers are the standard ports for accessing the service. In this case, we are exposing a HTTP service, so we will use port 80 (443 if you would like an SSL termination). -#### Via the OVH Control Panel: +#### Via the OVHcloud Control Panel: ![Adding a front-end dedicated to production, a blue front-end](images/frontend1.png){.thumbnail} @@ -215,7 +215,7 @@ This `front-end`{.action} is dedicated to accessing the production infrastructur This `front-end`{.action} is dedicated to accessing the development infrastructure. The ports exposed to your customers will be non-standard ports that you can choose arbitrarily. In this case, we will expose the HTTP development service on port 8888. -#### Via the OVH Control Panel: +#### Via the OVHcloud Control Panel: ![Add the green front-end, dedicated to development](images/frontend2.png){.thumbnail} @@ -242,7 +242,7 @@ This `front-end`{.action} is dedicated to accessing the development infrastructu Once you have finished configuring the components of the OVHcloud Load Balancer service, you now just need to apply your changes. -#### Via the OVH Control Panel: +#### Via the OVHcloud Control Panel: ![Apply your changes to the zone](images/deploy.png){.thumbnail} diff --git a/pages/network/load_balancer/case_blue_green/guide.fr-fr.md b/pages/network/load_balancer/case_blue_green/guide.fr-fr.md index 6c365817ac6..7b9c43fac09 100644 --- a/pages/network/load_balancer/case_blue_green/guide.fr-fr.md +++ b/pages/network/load_balancer/case_blue_green/guide.fr-fr.md @@ -6,19 +6,19 @@ updated: 2025-10-17 ## Objectif -Ce guide présente un cas d'usage spécifique du service Load Balancer OVHcloud : la configuration d'un service visant à faciliter le basculement fluide du trafic entre l'environnement de production et un nouvel environnement candidat à la production, également appelé infrastructure `blue-green`{.action}. +Ce guide présente un cas d'usage spécifique du service Load Balancer OVHcloud : la configuration d'un service visant à faciliter le basculement fluide du trafic entre l'environnement de production et un nouvel environnement candidat à la production, également appelé infrastructure **blue-green**. -Une infrastructure `blue-green`{.action} vous permet d'éviter toute interruption de service de votre infrastructure. Le principal avantage de ce type de déploiement est de pouvoir préparer des mises à jour et/ou des opérations de maintenance dans un environnement isolé de votre environnement de production. Vous pouvez ainsi tester vos modifications avant la mise en production, les annuler rapidement en cas de défaillance, et ce, avec une interruption de service quasi nulle. +Une infrastructure **blue-green** vous permet d'éviter toute interruption de service de votre infrastructure. Le principal avantage de ce type de déploiement est de pouvoir préparer des mises à jour et/ou des opérations de maintenance dans un environnement isolé de votre environnement de production. Vous pouvez ainsi tester vos modifications avant la mise en production, les annuler rapidement en cas de défaillance, et ce, avec une interruption de service quasi nulle. **Ce guide vous montre comment déployer une infrastructure blue-green avec le Load Balancer OVHcloud.** ## Prérequis -Pour déployer une infrastructure `blue-green`{.action}, vous avez besoin des composants suivants : +Pour déployer une infrastructure **blue-green**, vous avez besoin des composants suivants : - Un service [Load Balancer](/links/network/load-balancer) OVHcloud - Un accès au [Panneau de configuration OVHcloud](/links/manager) -- Deux [serveurs dédiés](/links/bare-metal/bare-metal) : un hébergeant votre environnement de production, et un serveur de configuration similaire hébergeant votre environnement de développement. +- Deux [serveurs dédiés](/links/bare-metal/bare-metal) : l'un hébergeant votre environnement de production, l'autre, un serveur de configuration similaire hébergeant votre environnement de développement. ## En pratique @@ -28,9 +28,9 @@ Vous disposez d'une infrastructure conçue pour héberger votre site Web en dire Cet environnement héberge le code de votre site Web, ainsi que toutes les applications essentielles (serveurs Web, serveurs de bases de données, etc.). Vous devez mettre à jour vos applications et/ou votre code régulièrement. Vous souhaitez pouvoir tester vos mises à jour sans impact sur la disponibilité ou la fonctionnalité du site Web pour les utilisateurs finaux. -Une façon d'y parvenir est de déployer une infrastructure `blue-green`{.action}. +Une façon d'y parvenir est de déployer une infrastructure **blue-green**. -Le principe d'un déploiement `blue-green`{.action} implique de pouvoir basculer facilement d'une infrastructure de développement à une infrastructure de production, et inversement. Ce basculement doit être transparent pour vos utilisateurs. Pour ce faire, le trafic public sera acheminé vers le port HTTP standard 80 pour l'accès à l'infrastructure de production, et un port non standard, tel que 8888, sera utilisé pour l'accès à l'infrastructure de développement. +Le principe d'un déploiement **blue-green** implique de pouvoir basculer facilement d'une infrastructure de développement à une infrastructure de production, et inversement. Ce basculement doit être transparent pour vos utilisateurs. Pour ce faire, le trafic public sera acheminé vers le port HTTP standard 80 pour l'accès à l'infrastructure de production, et un port non standard, tel que 8888, sera utilisé pour l'accès à l'infrastructure de développement. ## Déploiement des infrastructures @@ -40,7 +40,7 @@ L'infrastructure de production est accessible par vos clients sur le service HTT Au cours de la phase de configuration initiale, les rôles sont provisoirement attribués à chaque composant de l'infrastructure. L'`Infrastructure A`{.action} sert d'environnement de production initial, tandis que l'`infrastructure B`{.action} sert d'environnement de staging. À ce stade, nous allons les considérer comme similaires l'une à l'autre. -Une infrastructure `blue-green`{.action} implique le basculement de l'infrastructure A vers l'infrastructure B, une fois que l'infrastructure B est prête à exposer votre site Web après que vos modifications ont été appliquées et testées. Le Load Balancer gérera ce basculement. +Une infrastructure **blue-green** implique le basculement de l'infrastructure A vers l'infrastructure B, une fois que l'infrastructure B est prête à exposer votre site Web après que vos modifications ont été appliquées et testées. Le Load Balancer gérera ce basculement. Le schéma ci-dessous donne une idée générale de l'architecture : @@ -52,7 +52,7 @@ Cette infrastructure est composée d'une ferme de serveurs qui sera associée pl Dans notre scénario, nous allons déclarer une ferme de serveurs pour le service HTTP. Veuillez noter que vous pouvez créer autant de fermes (ainsi que de services TCP et/ou UDP) que nécessaire pour que votre service final soit exposé à vos clients. -#### Via le Panneau de configuration OVH : +#### Via le Panneau de configuration OVHcloud : ![Add a new HTTP farm dedicated to infrastructure A](images/ferme1.png){.thumbnail} @@ -63,7 +63,7 @@ Dans notre scénario, nous allons déclarer une ferme de serveurs pour le servic > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/farm > -|Setting|Meaning| +|Paramètre|Signification| |---|---| |serviceName|Votre ID de service Load Balancer| @@ -86,7 +86,7 @@ Avec les appels supplémentaires listés ci-dessous, vous pouvez respectivement Associez un serveur à votre ferme, s'il s'agit d'un serveur physique hébergeant votre infrastructure de production. Le service exposé au front-end est fourni par le port 8080 du serveur. Veuillez noter que vous pouvez associer un ou plusieurs serveurs à chaque ferme (pour équilibrer la charge et/ou offrir une tolérance aux pannes plus élevée, par ex.). -#### Via le Panneau de configuration OVH : +#### Via le Panneau de configuration OVHcloud : ![Add a new server to the farm HTTP A](images/serveur1.png){.thumbnail} @@ -149,7 +149,7 @@ Déployez la ferme de serveurs pour le service HTTP (et/ou tout autre service TC Associez un serveur à votre ferme. Ici, il s'agit d'un ou plusieurs serveurs physiques hébergeant votre infrastructure de développement. -#### Via le Panneau de configuration OVH : +#### Via le Panneau de configuration OVHcloud : ![Add a new server to the farm HTTP B](images/serveur2.png){.thumbnail} @@ -176,7 +176,7 @@ Associez un serveur à votre ferme. Ici, il s'agit d'un ou plusieurs serveurs ph ## Front-ends -La magie du déploiement `blue-green`{.action} réside dans la configuration de vos front-ends. À ce stade, nous avons configuré deux infrastructures fonctionnellement identiques. Pour les deux infrastructures, vous avez déclaré une ou plusieurs fermes de serveurs, chacune avec son propre ensemble de serveurs associés. +La magie du déploiement **blue-green** réside dans la configuration de vos front-ends. À ce stade, nous avons configuré deux infrastructures fonctionnellement identiques. Pour les deux infrastructures, vous avez déclaré une ou plusieurs fermes de serveurs, chacune avec son propre ensemble de serveurs associés. Pour basculer simplement d'une infrastructure à l'autre, nous utiliserons des front-ends. @@ -190,7 +190,7 @@ Pour ce faire, nous devons déclarer deux front-ends. Le premier vous donnera ac ### Front-end Blue Ce `front-end`{.action} est dédié à l'accès à l'infrastructure de production. Les ports exposés à vos clients sont les ports standard pour l'accès au service. Dans ce cas, nous exposons un service HTTP, nous utiliserons donc le port 80 (443 si vous souhaitez une terminaison SSL). -#### Via le Panneau de configuration OVH : +#### Via le Panneau de configuration OVHcloud : ![Adding a front-end dedicated to production, a blue front-end](images/frontend1.png){.thumbnail} @@ -215,7 +215,7 @@ Ce `front-end`{.action} est dédié à l'accès à l'infrastructure de productio Ce `front-end`{.action} est dédié à l'accès à l'infrastructure de développement. Les ports exposés à vos clients seront des ports non standard que vous pourrez choisir arbitrairement. Dans ce cas, nous exposerons le service de développement HTTP sur le port 8888. -#### Via le Panneau de configuration OVH : +#### Via le Panneau de configuration OVHcloud : ![Add the green front-end, dedicated to development](images/frontend2.png){.thumbnail} @@ -242,7 +242,7 @@ Ce `front-end`{.action} est dédié à l'accès à l'infrastructure de développ Une fois que vous avez terminé de configurer les composants du service Load Balancer OVHcloud, il ne vous reste plus qu'à appliquer vos modifications. -#### Via le Panneau de configuration OVH : +#### Via le Panneau de configuration OVHcloud : ![Apply your changes to the zone](images/deploy.png){.thumbnail} diff --git a/pages/network/load_balancer/case_smtp/guide.en-gb.md b/pages/network/load_balancer/case_smtp/guide.en-gb.md index b8553019049..5d1164aea17 100644 --- a/pages/network/load_balancer/case_smtp/guide.en-gb.md +++ b/pages/network/load_balancer/case_smtp/guide.en-gb.md @@ -32,7 +32,7 @@ In the Control Panel, you will see the features detailed below: ![OVHcloud Load Balancer service](images/iplb_service.png){.thumbnail} -Via the OVH API, in the section: +Via the OVHcloud API, in the section: > [!api] > diff --git a/pages/network/load_balancer/case_smtp/guide.fr-fr.md b/pages/network/load_balancer/case_smtp/guide.fr-fr.md index c9a59943e17..0b071d1c0f3 100644 --- a/pages/network/load_balancer/case_smtp/guide.fr-fr.md +++ b/pages/network/load_balancer/case_smtp/guide.fr-fr.md @@ -119,14 +119,14 @@ Les champs obligatoires sont l'*Adresse IPv4*, l'*État* et la *Version du Proxy > Postfix est compatible avec ce protocole. > -![Ajour d'un serveur dans une Ferme.](images/add_server.png){.thumbnail} -![Ajour d'un serveur dans une Ferme.](images/add_server_advance.png){.thumbnail} +![Ajout d'un serveur dans une ferme](images/add_server.png){.thumbnail} +![Ajout d'un serveur dans une ferme](images/add_server_advance.png){.thumbnail} Cliquez sur le bouton `Ajouter`{.action} une fois les champs remplis. Votre serveur devrait apparaître dans la liste des serveurs dans l'onglet `Fermes`{.action}, juste en dessous de la liste des fermes. -![Détails du serveur créé.](images/resume_server.png){.thumbnail} +![Détails du serveur créé](images/resume_server.png){.thumbnail} ### Depuis l'API OVHcloud diff --git a/pages/network/load_balancer/order_freecertificate/guide.en-gb.md b/pages/network/load_balancer/order_freecertificate/guide.en-gb.md index 13f3ee9709e..ad433b4f6f6 100644 --- a/pages/network/load_balancer/order_freecertificate/guide.en-gb.md +++ b/pages/network/load_balancer/order_freecertificate/guide.en-gb.md @@ -13,7 +13,7 @@ The purpose of SSL termination is to decrypt the incoming encrypted stream befor Handling SSL termination on the Load Balancer reduces the computational load on your backend servers and centralizes certificate management. This makes maintenance and security updates easier. -**Discover how to order a free SSL certificate via the OVHcloud Manager or the API.** +**Discover how to order a free SSL certificate via the OVHcloud Control Panel or the API.** ## Requirements @@ -22,7 +22,7 @@ Handling SSL termination on the Load Balancer reduces the computational load on ## Instructions -### Via the Manager +### Via the OVHcloud Control Panel #### Configure the frontend for SSL termination @@ -42,13 +42,13 @@ Once the frontend has been created, a banner will appear prompting you to `Apply #### Order the free SSL certificate -In the `SSL Certificates` section of your Manager, click the `Order SSL Certificate`{.action} button to create a new one. An edit window will appear with an `FQDN` field to be filled in. +In the `SSL Certificates` section of your Control Panel, click the `Order SSL Certificate`{.action} button to create a new one. An edit window will appear with an `FQDN` field to be filled in. ![Add a free SSL certificate](images/iplb-order-ssl.png){.thumbnail} #### Follow-up of the order -In the `Tasks`{.action} section of your Manager, the tasks related to ordering a free SSL Certificate are of the type `orderFreeCertificate`. +In the `Tasks`{.action} section of your Control Panel, the tasks related to ordering a free SSL Certificate are of the type `orderFreeCertificate`. ### Via API From 0065500ca4fd42a5757d48cd8457d265e9b7723b Mon Sep 17 00:00:00 2001 From: Slimane ALI Date: Mon, 20 Oct 2025 23:48:12 +0200 Subject: [PATCH 06/23] Requested changes (2) "Universe: cloud" removed as requested --- pages/network/load_balancer/order_freecertificate/guide.en-gb.md | 1 - pages/network/load_balancer/order_freecertificate/guide.fr-fr.md | 1 - 2 files changed, 2 deletions(-) diff --git a/pages/network/load_balancer/order_freecertificate/guide.en-gb.md b/pages/network/load_balancer/order_freecertificate/guide.en-gb.md index ad433b4f6f6..f49e711f71e 100644 --- a/pages/network/load_balancer/order_freecertificate/guide.en-gb.md +++ b/pages/network/load_balancer/order_freecertificate/guide.en-gb.md @@ -1,6 +1,5 @@ --- title: Order a free SSL certificate -universe: cloud excerpt: Order a free SSL certificate for your web services behind a Load Balancer updated: 2025-09-26 --- diff --git a/pages/network/load_balancer/order_freecertificate/guide.fr-fr.md b/pages/network/load_balancer/order_freecertificate/guide.fr-fr.md index 1001e8af786..e5a026d84e3 100644 --- a/pages/network/load_balancer/order_freecertificate/guide.fr-fr.md +++ b/pages/network/load_balancer/order_freecertificate/guide.fr-fr.md @@ -1,6 +1,5 @@ --- title: "Commande d'un certificat SSL gratuit" -universe: cloud excerpt: Commander un certificat SSL gratuit pour vos services web derrière un Load Balancer updated: 2025-09-26 --- From c790de59d11b266a9b54d3a14ade01fb91634384 Mon Sep 17 00:00:00 2001 From: Slimane ALI Date: Tue, 21 Oct 2025 12:08:48 +0200 Subject: [PATCH 07/23] Proofread blue-green/freecertificate --- .../case_blue_green/guide.en-gb.md | 47 ++++++++++--------- .../case_blue_green/guide.fr-fr.md | 35 +++++++------- .../order_freecertificate/guide.en-gb.md | 14 +++--- .../order_freecertificate/guide.fr-fr.md | 2 +- 4 files changed, 50 insertions(+), 48 deletions(-) diff --git a/pages/network/load_balancer/case_blue_green/guide.en-gb.md b/pages/network/load_balancer/case_blue_green/guide.en-gb.md index 7200634a9f7..f47c6ecb825 100644 --- a/pages/network/load_balancer/case_blue_green/guide.en-gb.md +++ b/pages/network/load_balancer/case_blue_green/guide.en-gb.md @@ -6,19 +6,19 @@ updated: 2025-10-17 ## Objective -This guide demonstrates a specific use case for the OVHcloud Load Balancer: the configuration of a service to facilitate seamless traffic switching between production and new production candidate environments, also called a **blue-green** infrastructure. +This guide demonstrates a specific use case for the OVHcloud Load Balancer: the configuration of a service to facilitate seamless traffic switching between production and new production candidate environments, also called a **blue-green infrastructure**. -With a **blue-green** infrastructure, you can stop your infrastructure from experiencing any downtime. The main benefit of this deployment type is that you can prepare updates and/or maintenance in an environment that is isolated from your production environment. This way, you can test your changes before they are put into production, undo them quickly if you detect any faults, and do all of this with virtually zero downtime. +With a blue-green infrastructure, you can stop your infrastructure from experiencing any downtime. The main benefit of this deployment type is that you can prepare updates and/or maintenance in an environment that is isolated from your production environment. This way, you can test your changes before they are put into production, undo them quickly if you detect any faults, and do all of this with virtually zero downtime. **This guide will show you how to deploy a blue-green infrastructure with the OVHcloud Load Balancer.** ## Requirements -To deploy a **blue-green** infrastructure, you need the following components: +To deploy a blue-green infrastructure, you need the following components: -- An OVHcloud [Load Balancer](/links/network/load-balancer) service +- An [OVHcloud Load Balancer](/links/network/load-balancer) service - Access to the [OVHcloud Control Panel](/links/manager) -- Two [dedicated servers](/links/bare-metal/bare-metal) : one hosting your production environment, and a similarly configured server hosting your development environment. +- Two [dedicated servers](/links/bare-metal/bare-metal), one hosting your production environment, and a similarly configured server hosting your staging environment. ## Instructions @@ -28,9 +28,9 @@ You have an infrastructure designed to host your live website. This environment hosts the website’s code, in addition to all essential applications (web servers, database servers, etc.). You need to update your applications and/or your code on a regular basis. You want to be able to test your updates without impacting the website's availability or functionality for end-users. -One way to achieve this is by deploying a **blue-green** infrastructure. +One way to achieve this is by deploying a blue-green infrastructure. -The principle of a **blue-green** deployment involves being able to switch easily from a development infrastructure to a production infrastructure, and vice versa. This switch must be done in a way that is transparent for your users. To do this, public traffic will be routed to the standard HTTP port 80 for access to the production infrastructure, and a non-standard port, such as 8888, will be used to access the development infrastructure. +The principle of a blue-green deployment involves being able to switch easily from a development infrastructure to a production infrastructure, and vice versa. This switch must be done in a way that is transparent for your users. To do this, public traffic will be routed to the standard HTTP port 80 for access to the production infrastructure, and a non-standard port, such as 8888, will be used to access the development infrastructure. ## Deploy the infrastructures @@ -38,9 +38,9 @@ In this scenario, your Load Balancer service plays a central role. It is the ele The production infrastructure can be accessed by your customers on the standard HTTP service (port 80), and your development infrastructure can be accessed by developers and admins on the non-standard port 8888. -During the initial setup phase, roles are provisionally assigned to each infrastructure component. `Infrastructure A`{.action} serves as the initial production environment, while `infrastructure B`{.action} serves as the staging environment. At this stage, we will consider them to be similar to one another. +During the initial setup phase, roles are provisionally assigned to each infrastructure component. **Infrastructure A** serves as the initial production environment, while **infrastructure B** serves as the staging environment. At this stage, we will consider them to be similar to one another. -A **blue-green** infrastructure involves switching from infrastructure A to infrastructure B, once infrastructure B has been fully updated and validated. The Load Balancer will manage this switch. +A blue-green infrastructure involves switching from infrastructure A to infrastructure B, once infrastructure B has been fully updated and validated. The Load Balancer will manage this switch. The diagram below gives a general idea of the architecture: @@ -84,7 +84,7 @@ With the additional calls listed below, you can list, modify and delete your ser > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/http/farm > -Associate a server with your farm, if it is a physical server hosting your production infrastructure. The service exposed to the front-end is supplied by the server’s port 8080. Please note that you can associate one or more servers with each farm (to balance the load and/or offer higher fault tolerance, for ex.). +Associate a dedicated server with your farm if it hosts your production infrastructure. The service is exposed to the front-end via the server’s port 8080. Note that you may associate one or more servers with each farm (for example, to balance the load or offer higher fault tolerance). #### Via the OVHcloud Control Panel: @@ -130,7 +130,7 @@ Functionally, this second infrastructure is identical to the first. It is also c Deploy the server farm for the HTTP service (and/or any other TCP or UDP services required for your final service to be exposed to your customers). -#### Via the Sunrise Control Panel: +#### Via the OVHcloud Control Panel: ![Add a new HTTP farm dedicated to infrastructure B](images/ferme2.png){.thumbnail} @@ -176,7 +176,7 @@ At this stage, here is the configuration status for your two farms: ## Front-ends -The magic of **blue-green** deployment lies in the configuration of your front-ends. At this stage, we have configure two functionally identical infrastructures. For both infrastructures, you have declared one or more server farms, each with their own set of associated servers. +The magic of blue-green deployment lies in the configuration of your front-ends. At this stage, we have configure two functionally identical infrastructures. For both infrastructures, you have declared one or more server farms, each with their own set of associated servers. To switch simply from one infrastructure to another, we will use front-ends. @@ -184,11 +184,12 @@ To do this, we need to declare two front-ends. The first one will give you acces > [!warning] > -> If the final service you expose to your customers requires several server farms (e.g. ports 80 and 443), you will need to declare a `front-end`{.action} for each of your farms. +> If the final service you expose to your customers requires several server farms (e.g. ports 80 and 443), you will need to declare a **front-end** for each of your farms. > ### Blue front-end -This `front-end`{.action} is dedicated to accessing the production infrastructure. The ports exposed to your customers are the standard ports for accessing the service. In this case, we are exposing a HTTP service, so we will use port 80 (443 if you would like an SSL termination). + +This **front-end** is dedicated to accessing the production infrastructure. The ports exposed to your customers are the standard ports for accessing the service. In this case, we are exposing a HTTP service, so we will use port 80 (443 if you would like an SSL termination). #### Via the OVHcloud Control Panel: @@ -213,7 +214,7 @@ This `front-end`{.action} is dedicated to accessing the production infrastructur ### Green front-end -This `front-end`{.action} is dedicated to accessing the development infrastructure. The ports exposed to your customers will be non-standard ports that you can choose arbitrarily. In this case, we will expose the HTTP development service on port 8888. +This **front-end** is dedicated to accessing the development infrastructure. The ports exposed to your customers will be non-standard ports that you can choose arbitrarily. In this case, we will expose the HTTP development service on port 8888. #### Via the OVHcloud Control Panel: @@ -265,22 +266,22 @@ Now, you need to switch over your front-ends from one server farm to another. Let’s take a look at our scenario: -- The production infrastructure (A) is deployed on `HTTP farm A`{.action} (id 77212), which in turn is attached to `HTTP server A`{.action}. This infrastructure can be accessed through the `blue front-end`{.action}. -- The development infrastructure (B) is deployed on `HTTP farm B`{.action} (id 77213), which in turn is attached to `HTTP server B`{.action}. This infrastructure can be accessed through the `green front-end`{.action}. +- The production infrastructure (A) is deployed on **HTTP farm A** (id 77212), which in turn is attached to **HTTP server A**. This infrastructure can be accessed through the **blue front-end**. +- The development infrastructure (B) is deployed on **HTTP farm B** (id 77213), which in turn is attached to **HTTP server B**. This infrastructure can be accessed through the **green front-end**. -Once you have modified/applied updates to `infrastructure B`{.action} and checked that the service is working properly, you decide to put it into production. +Once you have modified/applied updates to **infrastructure B** and checked that the service is working properly, you decide to put it into production. To switch between the two farms, you can simply update your different front-ends by modifying the ID of the farm it is attached to, and applying the modification. -The `blue front-end`{.action} (id 70089) will then be associated with `Farm B`{.action} (infrastructure B, new production, id 77213). +The **blue front-end** (id 70089) will then be associated with **Farm B** (infrastructure B, new production, id 77213). -The `green front-end`{.action} (id 70090) will then be associated with `Farm A`{.action} (infrastructure A, new development, id 77212). +The **green front-end** (id 70090) will then be associated with **Farm A** (infrastructure A, new development, id 77212). -This should be the result on the Sunrise Control Panel after updating the front-ends and applying the new configuration: +This should be the result on the OVHcloud Control Panel after updating the front-ends and applying the new configuration: ![Result after updating front-ends](images/switch.png){.thumbnail} -#### Via the API: updating front-ends and applying modifications#### +#### Via the API: updating front-ends and applying modifications > [!api] > @@ -317,7 +318,7 @@ This should be the result on the Sunrise Control Panel after updating the front- ## Conclusion -You have successfully implemented a highly available infrastructure for managing `blue-green deployments`{.action}. +You have successfully implemented a highly available infrastructure for managing blue-green deployments. Developers have access to a development environment on port 8888 (or any configurable non-standard port), while your customers continue to access the service in production via the standard HTTP port (80). diff --git a/pages/network/load_balancer/case_blue_green/guide.fr-fr.md b/pages/network/load_balancer/case_blue_green/guide.fr-fr.md index 7b9c43fac09..1c42fc186b0 100644 --- a/pages/network/load_balancer/case_blue_green/guide.fr-fr.md +++ b/pages/network/load_balancer/case_blue_green/guide.fr-fr.md @@ -16,9 +16,9 @@ Une infrastructure **blue-green** vous permet d'éviter toute interruption de se Pour déployer une infrastructure **blue-green**, vous avez besoin des composants suivants : -- Un service [Load Balancer](/links/network/load-balancer) OVHcloud +- Un service [Load Balancer OVHcloud](/links/network/load-balancer) - Un accès au [Panneau de configuration OVHcloud](/links/manager) -- Deux [serveurs dédiés](/links/bare-metal/bare-metal) : l'un hébergeant votre environnement de production, l'autre, un serveur de configuration similaire hébergeant votre environnement de développement. +- Deux [serveurs dédiés](/links/bare-metal/bare-metal), l'un hébergeant votre environnement de production, l'autre, un serveur de configuration similaire hébergeant votre environnement de développement. ## En pratique @@ -38,7 +38,7 @@ Dans ce scénario, votre service Load Balancer joue un rôle central. C'est l'é L'infrastructure de production est accessible par vos clients sur le service HTTP standard (port 80), et votre infrastructure de développement est accessible par les développeurs et administrateurs sur le port non standard 8888. -Au cours de la phase de configuration initiale, les rôles sont provisoirement attribués à chaque composant de l'infrastructure. L'`Infrastructure A`{.action} sert d'environnement de production initial, tandis que l'`infrastructure B`{.action} sert d'environnement de staging. À ce stade, nous allons les considérer comme similaires l'une à l'autre. +Au cours de la phase de configuration initiale, les rôles sont provisoirement attribués à chaque composant de l'infrastructure. **L'Infrastructure A** sert d'environnement de production initial, tandis que **l'infrastructure B** sert d'environnement de staging. À ce stade, nous allons les considérer comme similaires l'une à l'autre. Une infrastructure **blue-green** implique le basculement de l'infrastructure A vers l'infrastructure B, une fois que l'infrastructure B est prête à exposer votre site Web après que vos modifications ont été appliquées et testées. Le Load Balancer gérera ce basculement. @@ -84,7 +84,7 @@ Avec les appels supplémentaires listés ci-dessous, vous pouvez respectivement > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/http/farm > -Associez un serveur à votre ferme, s'il s'agit d'un serveur physique hébergeant votre infrastructure de production. Le service exposé au front-end est fourni par le port 8080 du serveur. Veuillez noter que vous pouvez associer un ou plusieurs serveurs à chaque ferme (pour équilibrer la charge et/ou offrir une tolérance aux pannes plus élevée, par ex.). +Associez un **serveur dédié** à votre ferme s'il héberge votre infrastructure de production. Le service est exposé au front-end via le port 8080 du serveur. Notez que vous pouvez associer un ou plusieurs serveurs à chaque ferme (par exemple, pour équilibrer la charge ou offrir une tolérance aux pannes plus élevée). #### Via le Panneau de configuration OVHcloud : @@ -130,7 +130,7 @@ Fonctionnellement, cette deuxième infrastructure est identique à la première. Déployez la ferme de serveurs pour le service HTTP (et/ou tout autre service TCP ou UDP requis pour que votre service final soit exposé à vos clients). -#### Via le Panneau de configuration Sunrise : +#### Via le Panneau de configuration OVHcloud : ![Add a new HTTP farm dedicated to infrastructure B](images/ferme2.png){.thumbnail} @@ -147,7 +147,7 @@ Déployez la ferme de serveurs pour le service HTTP (et/ou tout autre service TC |---|---| |serviceName|Votre ID de service Load Balancer| -Associez un serveur à votre ferme. Ici, il s'agit d'un ou plusieurs serveurs physiques hébergeant votre infrastructure de développement. +Associez un serveur à votre ferme. Ici, il s'agit d'un ou plusieurs **serveurs dédiés** hébergeant votre infrastructure de développement. #### Via le Panneau de configuration OVHcloud : @@ -184,11 +184,12 @@ Pour ce faire, nous devons déclarer deux front-ends. Le premier vous donnera ac > [!warning] > -> Si le service final que vous exposez à vos clients nécessite plusieurs fermes de serveurs (par ex. les ports 80 et 443), vous devrez déclarer un `front-end`{.action} pour chacune de vos fermes. +> Si le service final que vous exposez à vos clients nécessite plusieurs fermes de serveurs (par ex. les ports 80 et 443), vous devrez déclarer un **front-end** pour chacune de vos fermes. > ### Front-end Blue -Ce `front-end`{.action} est dédié à l'accès à l'infrastructure de production. Les ports exposés à vos clients sont les ports standard pour l'accès au service. Dans ce cas, nous exposons un service HTTP, nous utiliserons donc le port 80 (443 si vous souhaitez une terminaison SSL). + +Ce **front-end** est dédié à l'accès à l'infrastructure de production. Les ports exposés à vos clients sont les ports standard pour l'accès au service. Dans ce cas, nous exposons un service HTTP, nous utiliserons donc le port 80 (443 si vous souhaitez une terminaison SSL). #### Via le Panneau de configuration OVHcloud : @@ -213,7 +214,7 @@ Ce `front-end`{.action} est dédié à l'accès à l'infrastructure de productio ### Front-end Green -Ce `front-end`{.action} est dédié à l'accès à l'infrastructure de développement. Les ports exposés à vos clients seront des ports non standard que vous pourrez choisir arbitrairement. Dans ce cas, nous exposerons le service de développement HTTP sur le port 8888. +Ce **front-end** est dédié à l'accès à l'infrastructure de développement. Les ports exposés à vos clients seront des ports non standard que vous pourrez choisir arbitrairement. Dans ce cas, nous exposerons le service de développement HTTP sur le port 8888. #### Via le Panneau de configuration OVHcloud : @@ -265,22 +266,22 @@ Maintenant, vous devez basculer vos front-ends d'une ferme de serveurs à une au Prenons notre scénario : -- L'infrastructure de production (A) est déployée sur la `ferme HTTP A`{.action} (id 77212), qui est elle-même attachée au `serveur HTTP A`{.action}. Cette infrastructure est accessible via le `front-end blue`{.action}. -- L'infrastructure de développement (B) est déployée sur la `ferme HTTP B`{.action} (id 77213), qui est elle-même attachée au `serveur HTTP B`{.action}. Cette infrastructure est accessible via le `front-end green`{.action}. +- L'infrastructure de production (A) est déployée sur la **ferme HTTP A** (id 77212), qui est elle-même attachée au **serveur HTTP A**. Cette infrastructure est accessible via le **front-end blue**. +- L'infrastructure de développement (B) est déployée sur la **ferme HTTP B** (id 77213), qui est elle-même attachée au **serveur HTTP B**. Cette infrastructure est accessible via le **front-end green**. -Une fois que vous avez modifié/appliqué les mises à jour à l'`infrastructure B`{.action} et vérifié que le service fonctionne correctement, vous décidez de la mettre en production. +Une fois que vous avez modifié/appliqué les mises à jour à l'**infrastructure B** et vérifié que le service fonctionne correctement, vous décidez de la mettre en production. Pour basculer entre les deux fermes, vous pouvez simplement mettre à jour vos différents front-ends en modifiant l'ID de la ferme à laquelle il est attaché, et en appliquant la modification. -Le `front-end blue`{.action} (id 70089) sera alors associé à la `Ferme B`{.action} (infrastructure B, nouvelle production, id 77213). +Le **front-end blue** (id 70089) sera alors associé à la **Ferme B** (infrastructure B, nouvelle production, id 77213). -Le `front-end green`{.action} (id 70090) sera alors associé à la `Ferme A`{.action} (infrastructure A, nouveau développement, id 77212). +Le **front-end green** (id 70090) sera alors associé à la **Ferme A** (infrastructure A, nouveau développement, id 77212). -Voici le résultat attendu sur le Panneau de configuration Sunrise après la mise à jour des front-ends et l'application de la nouvelle configuration : +Voici le résultat attendu sur le Panneau de configuration OVHcloud après la mise à jour des front-ends et l'application de la nouvelle configuration : ![Result after updating front-ends](images/switch.png){.thumbnail} -#### Via l'API : mise à jour des front-ends et application des modifications #### +#### Via l'API : mise à jour des front-ends et application des modifications > [!api] > @@ -317,7 +318,7 @@ Voici le résultat attendu sur le Panneau de configuration Sunrise après la mis ## Conclusion -Vous avez réussi à mettre en œuvre une infrastructure hautement disponible pour la gestion des `déploiements blue-green`{.action}. +Vous avez réussi à mettre en œuvre une infrastructure hautement disponible pour la gestion des déploiements blue-green. Les développeurs ont accès à un environnement de développement sur le port 8888 (ou tout port non standard configurable), tandis que vos clients continuent d'accéder au service en production via le port HTTP standard (80). diff --git a/pages/network/load_balancer/order_freecertificate/guide.en-gb.md b/pages/network/load_balancer/order_freecertificate/guide.en-gb.md index f49e711f71e..d65968df4bd 100644 --- a/pages/network/load_balancer/order_freecertificate/guide.en-gb.md +++ b/pages/network/load_balancer/order_freecertificate/guide.en-gb.md @@ -6,7 +6,7 @@ updated: 2025-09-26 ## Objective -The OVH Load Balancer service can be configured to support SSL termination. +The OVHcloud Load Balancer service can be configured to support SSL termination. The purpose of SSL termination is to decrypt the incoming encrypted stream before forwarding it to the appropriate service, such as a web server. @@ -17,7 +17,7 @@ Handling SSL termination on the Load Balancer reduces the computational load on ## Requirements - You must have an [OVHcloud Load balancer](/links/network/load-balancer) in your OVHcloud account. -- You must be logged in to the [OVH Control Panel](/links/manager). +- You must be logged in to the [OVHcloud Control Panel](/links/manager). ## Instructions @@ -49,7 +49,7 @@ In the `SSL Certificates` section of your Control Panel, click the `Order SSL Ce In the `Tasks`{.action} section of your Control Panel, the tasks related to ordering a free SSL Certificate are of the type `orderFreeCertificate`. -### Via API +### Via the API #### Configuring the frontend for SSL termination @@ -75,11 +75,11 @@ In the API, the command is as follows : > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/freeCertificate > -For the order to be finalized, the chosen domain name must point to your OVH Load Balancer service. +For the order to be finalized, the chosen domain name must point to your OVHcloud Load Balancer service. #### Follow-up of the order -- Returning the task list +- Returning the task list You can specify the action type `orderFreeCertificate` to refine the search. @@ -88,14 +88,14 @@ You can specify the action type `orderFreeCertificate` to refine the search. > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/task > -- Returning the status of a particular task +- Returning the status of a particular task > [!api] > > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/task/{id} > -Once the order is complete, the SSL Certificate is automatically installed on your OVH Load Balancer service. +Once the order is complete, the SSL Certificate is automatically installed on your OVHcloud Load Balancer service. ## Go further diff --git a/pages/network/load_balancer/order_freecertificate/guide.fr-fr.md b/pages/network/load_balancer/order_freecertificate/guide.fr-fr.md index e5a026d84e3..dc3da1db0a5 100644 --- a/pages/network/load_balancer/order_freecertificate/guide.fr-fr.md +++ b/pages/network/load_balancer/order_freecertificate/guide.fr-fr.md @@ -6,7 +6,7 @@ updated: 2025-09-26 ## Objectif -Le service OVH Load Balancer peut être configuré pour prendre en charge la terminaison SSL. +Le service OVHcloud Load Balancer peut être configuré pour prendre en charge la terminaison SSL. La terminaison SSL a pour but de déchiffrer le flux chiffré entrant avant de le faire suivre vers le service approprié, tel qu'un serveur web. From 7bef374b57fca2eb9941bec6c3068a150c79d758 Mon Sep 17 00:00:00 2001 From: Slimane ALI Date: Tue, 21 Oct 2025 12:27:02 +0200 Subject: [PATCH 08/23] Proofread case_smtp/create_balancing --- pages/network/load_balancer/case_smtp/guide.en-gb.md | 8 +++++--- pages/network/load_balancer/case_smtp/guide.fr-fr.md | 6 +++--- .../load_balancer/create_balancing/guide.fr-fr.md | 12 ++++++------ 3 files changed, 14 insertions(+), 12 deletions(-) diff --git a/pages/network/load_balancer/case_smtp/guide.en-gb.md b/pages/network/load_balancer/case_smtp/guide.en-gb.md index 5d1164aea17..3c10c918aeb 100644 --- a/pages/network/load_balancer/case_smtp/guide.en-gb.md +++ b/pages/network/load_balancer/case_smtp/guide.en-gb.md @@ -70,7 +70,7 @@ Your server farm should appear in the list, in the `Farms`{.action} tab. > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/tcp/farm > -- Details of a specific TCP server: +- Details of a specific TCP server farm: > [!api] > @@ -166,7 +166,7 @@ A `front-end`{.action} must now be added to the service and connected to the ser Go to the `+ Front-ends`{.action} tab, and click `+TCP/TLS`{.action}. -Fill in the fields. The mandatory fields for a basic configuration are *Port* (25 for a standard SMTP service), *Zone* and *Probe* (if a probe was configured on your farm). If you want your service to be available across several ports at once, you can specify a list of ports, separated by commas, or a port range, in the format "start_port-end_port". +Fill in the fields. The mandatory fields for a basic configuration are *Port* (25 for a standard SMTP service), *Zone*, *Default farm* and *Probe* (if a probe was configured on your farm). If you want your service to be available across several ports at once, you can specify a list of ports, separated by commas, or a port range, in the format "-". If you have routed Additional IPs to your OVHcloud Load Balancer service, you can also attach a front-end to one or more specific Additional IPs. @@ -240,7 +240,9 @@ Go to the homepage for the OVHcloud Load Balancer, and click `Apply:Zone`{.actio To make Postfix compatible with HAProxy *ProxyProtocol*, an option is required in the postfix main.cf configuration file: -**smtp_upstream_proxy_protocol = haproxy** +```bash +smtp_upstream_proxy_protocol = haproxy +``` The Postfix daemon must then be restarted. diff --git a/pages/network/load_balancer/case_smtp/guide.fr-fr.md b/pages/network/load_balancer/case_smtp/guide.fr-fr.md index 0b071d1c0f3..74f45285703 100644 --- a/pages/network/load_balancer/case_smtp/guide.fr-fr.md +++ b/pages/network/load_balancer/case_smtp/guide.fr-fr.md @@ -68,14 +68,14 @@ Votre ferme de serveurs devrait apparaître dans la liste, sous l'onglet `Fermes #### Depuis l'API OVHcloud -- Liste des Fermes de serveurs TCP : +- Liste des fermes de serveurs TCP : > [!api] > > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/tcp/farm > -- Détails d'un serveur TCP spécifique : +- Détails d'une ferme de serveurs TCP : > [!api] > @@ -173,7 +173,7 @@ Un *frontend* doit maintenant être ajouté à notre service et connecté à la Dans l'onglet `+Frontends`{.action}, cliquez sur le bouton `+TCP/TLS`{.action}. -Remplissez les différents champs. Les seuls champs obligatoires pour une configuration simple sont le *Port* (25 pour un service SMTP standard), la *Zone* et la *Sonde* (si vous en avez configuré une dans votre Ferme). Si vous souhaitez que votre service soit disponible sur plusieurs ports en même temps, vous pouvez spécifier une liste de ports séparés par des virgules ou une plage de ports de la forme "-". +Remplissez les différents champs. Les seuls champs obligatoires pour une configuration simple sont le *Port* (25 pour un service SMTP standard), la *Zone*, la *Ferme par défaut* et la *Sonde* (si vous en avez configuré une dans votre Ferme). Si vous souhaitez que votre service soit disponible sur plusieurs ports en même temps, vous pouvez spécifier une liste de ports séparés par des virgules ou une plage de ports de la forme "-". Si vous avez routé des Additional IP vers votre service OVHcloud Load Balancer, vous pouvez également attacher un *frontend* à une ou plusieurs Additional IP spécifiques. diff --git a/pages/network/load_balancer/create_balancing/guide.fr-fr.md b/pages/network/load_balancer/create_balancing/guide.fr-fr.md index 492f2203216..af304b13075 100644 --- a/pages/network/load_balancer/create_balancing/guide.fr-fr.md +++ b/pages/network/load_balancer/create_balancing/guide.fr-fr.md @@ -61,8 +61,8 @@ Cet appel permet de consulter le détail d'une ferme en connaissant son identifi |Paramètre|Signification| |---|---| -|serviceName\*|Identifiant de votre service Load Balancer| -|farmId\*|Identifiant numérique de la ferme| +|serviceName*|Identifiant de votre service Load Balancer| +|farmId*|Identifiant numérique de la ferme| |Réponse (BackendHttp)|Signification| |---|---| @@ -85,8 +85,8 @@ Cet appel permet de modifier la configuration d'une ferme en connaissant son ide |Paramètre|Signification| |---|---| -|serviceName\*|Identifiant de votre service Load Balancer| -|farmId\*|Identifiant numérique de la ferme| +|serviceName*|Identifiant de votre service Load Balancer| +|farmId*|Identifiant numérique de la ferme| |BackendHttp.balance|Algorithme de répartition souhaité pour cette ferme| #### Appliquer les modifications @@ -98,8 +98,8 @@ Cet appel permet de modifier la configuration d'une ferme en connaissant son ide |Paramètre|Signification| |---|---| -|serviceName\*|Identifiant de votre service Load Balancer| -|zone\*|Nom de la zone dans laquelle déployer la configuration| +|serviceName*|Identifiant de votre service Load Balancer| +|zone*|Nom de la zone dans laquelle déployer la configuration| ## Aller plus loin From 262886a8be9365b205f5dd9df1354e8df47d20a9 Mon Sep 17 00:00:00 2001 From: Slimane ALI Date: Tue, 21 Oct 2025 12:41:24 +0200 Subject: [PATCH 09/23] Table headers --- .../case_blue_green/guide.fr-fr.md | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/pages/network/load_balancer/case_blue_green/guide.fr-fr.md b/pages/network/load_balancer/case_blue_green/guide.fr-fr.md index 1c42fc186b0..ca985d2c22c 100644 --- a/pages/network/load_balancer/case_blue_green/guide.fr-fr.md +++ b/pages/network/load_balancer/case_blue_green/guide.fr-fr.md @@ -99,7 +99,7 @@ Associez un **serveur dédié** à votre ferme s'il héberge votre infrastructur > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/farm/{farmId}/server > -|Setting|Required|Meaning|Example| +|Paramètre|Requis|Signification|Exemple| |---|---|---|---| |serviceName|Requis|Votre ID de service Load Balancer|loadbalancer-abcdef0123456789| |farmId|Requis|Votre ID de ferme de serveurs|77212| @@ -143,7 +143,7 @@ Déployez la ferme de serveurs pour le service HTTP (et/ou tout autre service TC > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/farm > -|Setting|Meaning| +|Paramètre|Signification| |---|---| |serviceName|Votre ID de service Load Balancer| @@ -162,7 +162,7 @@ Associez un serveur à votre ferme. Ici, il s'agit d'un ou plusieurs **serveurs > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/farm/{farmId}/server > -|Setting|Required|Meaning|Example| +|Paramètre|Requis|Signification|Exemple| |---|---|---|---| |serviceName|Requis|Votre ID de service Load Balancer|loadbalancer-abcdef0123456789| |farmId|Requis|Votre ID de ferme de serveurs|77213| @@ -204,7 +204,7 @@ Ce **front-end** est dédié à l'accès à l'infrastructure de production. Les > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/frontend > -|Setting|Required|Meaning|Example| +|Paramètre|Requis|Signification|Exemple| |---|---|---|---| |serviceName|Requis|Votre ID de service Load Balancer|loadbalancer-abcdef0123456789| |defaultFarmId||Votre ID de ferme de production|77212| @@ -229,7 +229,7 @@ Ce **front-end** est dédié à l'accès à l'infrastructure de développement. > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/frontend > -|Setting|Required|Meaning|Example| +|Paramètre|Requis|Signification|Exemple| |---|---|---|---| |serviceName|Requis|Votre ID de service Load Balancer|loadbalancer-abcdef0123456789| |defaultFarmId||Votre ID de ferme de production|77213| @@ -254,7 +254,7 @@ Une fois que vous avez terminé de configurer les composants du service Load Bal > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh > -|Setting|Meaning| +|Paramètre|Signification| |---|---| |serviceName|Votre ID de service Load Balancer| @@ -288,7 +288,7 @@ Voici le résultat attendu sur le Panneau de configuration OVHcloud après la mi > @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/http/frontend/{frontendId} > -|Setting|Meaning|Example| +|Paramètre|Signification|Exemple| |---|---|---| |serviceName|Votre ID de service Load Balancer|loadbalancer-abcdef0123456789| |frontendId|Votre ID de front-end de production|70089| @@ -299,7 +299,7 @@ Voici le résultat attendu sur le Panneau de configuration OVHcloud après la mi > @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/http/frontend/{frontendId} > -|Setting|Meaning|Example| +|Paramètre|Signification|Exemple| |---|---|---| |serviceName|Votre ID de service Load Balancer|loadbalancer-abcdef0123456789| |frontendId|Votre ID de front-end de production|70090| @@ -312,7 +312,7 @@ Voici le résultat attendu sur le Panneau de configuration OVHcloud après la mi > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh > -|Setting|Meaning| +|Paramètre|Signification| |---|---| |serviceName|Votre ID de service Load Balancer| From fed388681a22a2c68872e7c0ed58b2da0b8ebd58 Mon Sep 17 00:00:00 2001 From: Montrealhub <89825661+Jessica41@users.noreply.github.com> Date: Tue, 21 Oct 2025 13:59:27 -0400 Subject: [PATCH 10/23] first proof guide.en-gb.md --- .../case_blue_green/guide.en-gb.md | 54 +++++++++---------- 1 file changed, 26 insertions(+), 28 deletions(-) diff --git a/pages/network/load_balancer/case_blue_green/guide.en-gb.md b/pages/network/load_balancer/case_blue_green/guide.en-gb.md index f47c6ecb825..9684209b85f 100644 --- a/pages/network/load_balancer/case_blue_green/guide.en-gb.md +++ b/pages/network/load_balancer/case_blue_green/guide.en-gb.md @@ -1,7 +1,7 @@ --- title: 'Deploying a blue-green infrastructure' excerpt: 'This guide will show you how to deploy a blue-green infrastructure with the OVHcloud Load Balancer' -updated: 2025-10-17 +updated: 2025-10-21 --- ## Objective @@ -48,15 +48,15 @@ The diagram below gives a general idea of the architecture: ### Infrastructure A -This infrastructure is made up of a server farm that will later be associated with a front-end of your Load Balancer. This farm will expose an HTTP, TCP or UDP service to the front-end. It also balances loads by sending the front-end’s incoming traffic to the servers. For more detail on the role of various component of the OVHcloud Load Balancer service, you can read the following guide: [Introduction to the OVHcloud Load Balancer](/pages/network/load_balancer/use_presentation). +This infrastructure is made up of a server farm that will later be associated with a front-end of your Load Balancer. This farm will expose an HTTP, TCP or UDP service to the front-end. It also balances loads by sending the front-end’s incoming traffic to the servers. For more details on the role of the various components of the OVHcloud Load Balancer service, please refer to the following guide: [Introduction to the OVHcloud Load Balancer](/pages/network/load_balancer/use_presentation). In our scenario, we will declare a farm of servers for the HTTP service. Please note that you can create as many farms (as well as TCP and/or UDP services) as are required for your final service to be exposed to your customers. -#### Via the OVHcloud Control Panel: +#### Via the OVHcloud Control Panel ![Add a new HTTP farm dedicated to infrastructure A](images/ferme1.png){.thumbnail} -#### Via the API: +#### Via the API > [!api] > @@ -67,7 +67,7 @@ In our scenario, we will declare a farm of servers for the HTTP service. Please |---|---| |serviceName|Your Load Balancer service ID| -With the additional calls listed below, you can list, modify and delete your server farms respectively. +With the additional calls listed below, you can list, modify and delete your server farms respectively: > [!api] > @@ -84,15 +84,15 @@ With the additional calls listed below, you can list, modify and delete your ser > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/http/farm > -Associate a dedicated server with your farm if it hosts your production infrastructure. The service is exposed to the front-end via the server’s port 8080. Note that you may associate one or more servers with each farm (for example, to balance the load or offer higher fault tolerance). +Link a dedicated server to your farm if it hosts your production infrastructure. The service is exposed to the front-end via the server’s port 8080. Note that you may LINK one or more servers with each farm (for example, to balance the load or offer higher fault tolerance). -#### Via the OVHcloud Control Panel: +#### Via the OVHcloud Control Panel ![Add a new server to the farm HTTP A](images/serveur1.png){.thumbnail} ![Enter the HTTP A server’s configuration](images/server1.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -107,7 +107,7 @@ Associate a dedicated server with your farm if it hosts your production infrastr |displayName||The name of the server associated with your farm|HTTP A server| |port||The server port associated with your farm|8080| -With the additional calls listed below, you can list, modify and delete your servers respectively. +With the additional calls listed below, you can list, modify and delete your servers respectively: > [!api] > @@ -130,13 +130,13 @@ Functionally, this second infrastructure is identical to the first. It is also c Deploy the server farm for the HTTP service (and/or any other TCP or UDP services required for your final service to be exposed to your customers). -#### Via the OVHcloud Control Panel: +#### Via the OVHcloud Control Panel ![Add a new HTTP farm dedicated to infrastructure B](images/ferme2.png){.thumbnail} ![Create a second farm dedicated to infrastructure B](images/backend2.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -149,13 +149,13 @@ Deploy the server farm for the HTTP service (and/or any other TCP or UDP service Associate a server with your farm. Here, it involves one or more physical servers hosting your development infrastructure. -#### Via the OVHcloud Control Panel: +#### Via the OVHcloud Control Panel ![Add a new server to the farm HTTP B](images/serveur2.png){.thumbnail} ![Enter the HTTP B server’s configuration](images/server2.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -176,7 +176,7 @@ At this stage, here is the configuration status for your two farms: ## Front-ends -The magic of blue-green deployment lies in the configuration of your front-ends. At this stage, we have configure two functionally identical infrastructures. For both infrastructures, you have declared one or more server farms, each with their own set of associated servers. +The magic of blue-green deployment lies in the configuration of your front-ends. At this stage, we have configured two functionally identical infrastructures. For both infrastructures, you have declared one or more server farms, each with their own set of associated servers. To switch simply from one infrastructure to another, we will use front-ends. @@ -189,15 +189,15 @@ To do this, we need to declare two front-ends. The first one will give you acces ### Blue front-end -This **front-end** is dedicated to accessing the production infrastructure. The ports exposed to your customers are the standard ports for accessing the service. In this case, we are exposing a HTTP service, so we will use port 80 (443 if you would like an SSL termination). +This **front-end** is dedicated to accessing the production infrastructure. The ports exposed to your customers are the standard ports for accessing the service. In this case, we are exposing an HTTP service, so we will use port 80 (443 if you would like an SSL termination). -#### Via the OVHcloud Control Panel: +#### Via the OVHcloud Control Panel ![Adding a front-end dedicated to production, a blue front-end](images/frontend1.png){.thumbnail} ![Enter the blue front-end’s configuration](images/fblue.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -216,13 +216,13 @@ This **front-end** is dedicated to accessing the production infrastructure. The This **front-end** is dedicated to accessing the development infrastructure. The ports exposed to your customers will be non-standard ports that you can choose arbitrarily. In this case, we will expose the HTTP development service on port 8888. -#### Via the OVHcloud Control Panel: +#### Via the OVHcloud Control Panel ![Add the green front-end, dedicated to development](images/frontend2.png){.thumbnail} ![Enter the green front-end’s configuration](images/fgreen.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -241,13 +241,13 @@ This **front-end** is dedicated to accessing the development infrastructure. The ### Initial deployment -Once you have finished configuring the components of the OVHcloud Load Balancer service, you now just need to apply your changes. +Once you have finished configuring the components of the OVHcloud Load Balancer service, the only thing left to do is apply your changes. -#### Via the OVHcloud Control Panel: +#### Via the OVHcloud Control Panel ![Apply your changes to the zone](images/deploy.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -260,16 +260,14 @@ Once you have finished configuring the components of the OVHcloud Load Balancer ### The production/staging switch -At this stage, our initial environment is deployed and ready to use. - -Now, you need to switch over your front-ends from one server farm to another. +At this stage, our initial environment is deployed and ready to use. Now, you need to switch over your front-ends from one server farm to another. Let’s take a look at our scenario: - The production infrastructure (A) is deployed on **HTTP farm A** (id 77212), which in turn is attached to **HTTP server A**. This infrastructure can be accessed through the **blue front-end**. - The development infrastructure (B) is deployed on **HTTP farm B** (id 77213), which in turn is attached to **HTTP server B**. This infrastructure can be accessed through the **green front-end**. -Once you have modified/applied updates to **infrastructure B** and checked that the service is working properly, you decide to put it into production. +Once you have modified/applied updates to **infrastructure B** and checked that the service is working properly, you can decide to put it into production. To switch between the two farms, you can simply update your different front-ends by modifying the ID of the farm it is attached to, and applying the modification. @@ -281,7 +279,7 @@ This should be the result on the OVHcloud Control Panel after updating the front ![Result after updating front-ends](images/switch.png){.thumbnail} -#### Via the API: updating front-ends and applying modifications +#### Via the OVHcloud API: updating front-ends and applying modifications > [!api] > @@ -328,4 +326,4 @@ Another way to consolidate your infrastructure even further is by multiplying th ## Go further -Join our [community of users](/links/community). \ No newline at end of file +Join our [community of users](/links/community). From 10b777a730e5fecfbfe78eb61664e0446bb73f5d Mon Sep 17 00:00:00 2001 From: Montrealhub <89825661+Jessica41@users.noreply.github.com> Date: Tue, 21 Oct 2025 18:50:00 -0400 Subject: [PATCH 11/23] first proof guide.fr-fr.md --- .../case_blue_green/guide.fr-fr.md | 52 +++++++++---------- 1 file changed, 25 insertions(+), 27 deletions(-) diff --git a/pages/network/load_balancer/case_blue_green/guide.fr-fr.md b/pages/network/load_balancer/case_blue_green/guide.fr-fr.md index ca985d2c22c..87ee236d301 100644 --- a/pages/network/load_balancer/case_blue_green/guide.fr-fr.md +++ b/pages/network/load_balancer/case_blue_green/guide.fr-fr.md @@ -1,7 +1,7 @@ --- title: "Déploiement d'une infrastructure blue-green" excerpt: "Ce guide vous montre comment déployer une infrastructure blue-green avec le Load Balancer OVHcloud" -updated: 2025-10-17 +updated: 2025-10-21 --- ## Objectif @@ -17,7 +17,7 @@ Une infrastructure **blue-green** vous permet d'éviter toute interruption de se Pour déployer une infrastructure **blue-green**, vous avez besoin des composants suivants : - Un service [Load Balancer OVHcloud](/links/network/load-balancer) -- Un accès au [Panneau de configuration OVHcloud](/links/manager) +- Un accès à l'[espace client OVHcloud](/links/manager) - Deux [serveurs dédiés](/links/bare-metal/bare-metal), l'un hébergeant votre environnement de production, l'autre, un serveur de configuration similaire hébergeant votre environnement de développement. ## En pratique @@ -50,13 +50,13 @@ Le schéma ci-dessous donne une idée générale de l'architecture : Cette infrastructure est composée d'une ferme de serveurs qui sera associée plus tard à un front-end de votre Load Balancer. Cette ferme exposera un service HTTP, TCP ou UDP au front-end. Elle assure également l'équilibrage de charge en envoyant le trafic entrant du front-end aux serveurs. Pour plus de détails sur le rôle des différents composants du service Load Balancer OVHcloud, vous pouvez lire le guide suivant : [Introduction au Load Balancer OVHcloud](/pages/network/load_balancer/use_presentation). -Dans notre scénario, nous allons déclarer une ferme de serveurs pour le service HTTP. Veuillez noter que vous pouvez créer autant de fermes (ainsi que de services TCP et/ou UDP) que nécessaire pour que votre service final soit exposé à vos clients. +Dans notre scénario, nous allons déclarer une ferme de serveurs pour le service HTTP. Veuillez noter que vous pouvez créer autant de fermes (ainsi que de services TCP et/ou UDP) que nécessaire pour que votre service final soit accessible à vos clients. -#### Via le Panneau de configuration OVHcloud : +#### Via l'espace client OVHcloud ![Add a new HTTP farm dedicated to infrastructure A](images/ferme1.png){.thumbnail} -#### Via l'API : +#### Via l'API OVHcloud > [!api] > @@ -67,7 +67,7 @@ Dans notre scénario, nous allons déclarer une ferme de serveurs pour le servic |---|---| |serviceName|Votre ID de service Load Balancer| -Avec les appels supplémentaires listés ci-dessous, vous pouvez respectivement lister, modifier et supprimer vos fermes de serveurs. +Avec les appels supplémentaires listés ci-dessous, vous pouvez respectivement lister, modifier et supprimer vos fermes de serveurs: > [!api] > @@ -86,13 +86,13 @@ Avec les appels supplémentaires listés ci-dessous, vous pouvez respectivement Associez un **serveur dédié** à votre ferme s'il héberge votre infrastructure de production. Le service est exposé au front-end via le port 8080 du serveur. Notez que vous pouvez associer un ou plusieurs serveurs à chaque ferme (par exemple, pour équilibrer la charge ou offrir une tolérance aux pannes plus élevée). -#### Via le Panneau de configuration OVHcloud : +#### Via l'espace client OVHcloud ![Add a new server to the farm HTTP A](images/serveur1.png){.thumbnail} ![Enter the HTTP A server’s configuration](images/server1.png){.thumbnail} -#### Via l'API : +#### Via l'API OVHcloud > [!api] > @@ -107,7 +107,7 @@ Associez un **serveur dédié** à votre ferme s'il héberge votre infrastructur |displayName||Le nom du serveur associé à votre ferme|HTTP A server| |port||Le port du serveur associé à votre ferme|8080| -Avec les appels supplémentaires listés ci-dessous, vous pouvez respectivement lister, modifier et supprimer vos serveurs. +Avec les appels supplémentaires listés ci-dessous, vous pouvez respectivement lister, modifier et supprimer vos serveurs: > [!api] > @@ -130,13 +130,13 @@ Fonctionnellement, cette deuxième infrastructure est identique à la première. Déployez la ferme de serveurs pour le service HTTP (et/ou tout autre service TCP ou UDP requis pour que votre service final soit exposé à vos clients). -#### Via le Panneau de configuration OVHcloud : +#### Via l'espace client OVHcloud ![Add a new HTTP farm dedicated to infrastructure B](images/ferme2.png){.thumbnail} ![Create a second farm dedicated to infrastructure B](images/backend2.png){.thumbnail} -#### Via l'API : +#### Via l'API OVHcloud > [!api] > @@ -149,13 +149,13 @@ Déployez la ferme de serveurs pour le service HTTP (et/ou tout autre service TC Associez un serveur à votre ferme. Ici, il s'agit d'un ou plusieurs **serveurs dédiés** hébergeant votre infrastructure de développement. -#### Via le Panneau de configuration OVHcloud : +#### Via l'espace client OVHcloud ![Add a new server to the farm HTTP B](images/serveur2.png){.thumbnail} ![Enter the HTTP B server’s configuration](images/server2.png){.thumbnail} -#### Via l'API : +#### Via l'API OVHcloud > [!api] > @@ -191,13 +191,13 @@ Pour ce faire, nous devons déclarer deux front-ends. Le premier vous donnera ac Ce **front-end** est dédié à l'accès à l'infrastructure de production. Les ports exposés à vos clients sont les ports standard pour l'accès au service. Dans ce cas, nous exposons un service HTTP, nous utiliserons donc le port 80 (443 si vous souhaitez une terminaison SSL). -#### Via le Panneau de configuration OVHcloud : +#### Via l'espace client OVHcloud ![Adding a front-end dedicated to production, a blue front-end](images/frontend1.png){.thumbnail} ![Enter the blue front-end’s configuration](images/fblue.png){.thumbnail} -#### Via l'API : +#### Via l'API OVHcloud > [!api] > @@ -216,13 +216,13 @@ Ce **front-end** est dédié à l'accès à l'infrastructure de production. Les Ce **front-end** est dédié à l'accès à l'infrastructure de développement. Les ports exposés à vos clients seront des ports non standard que vous pourrez choisir arbitrairement. Dans ce cas, nous exposerons le service de développement HTTP sur le port 8888. -#### Via le Panneau de configuration OVHcloud : +#### Via l'espace client OVHcloud ![Add the green front-end, dedicated to development](images/frontend2.png){.thumbnail} ![Enter the green front-end’s configuration](images/fgreen.png){.thumbnail} -#### Via l'API : +#### Via l'API OVHcloud > [!api] > @@ -243,11 +243,11 @@ Ce **front-end** est dédié à l'accès à l'infrastructure de développement. Une fois que vous avez terminé de configurer les composants du service Load Balancer OVHcloud, il ne vous reste plus qu'à appliquer vos modifications. -#### Via le Panneau de configuration OVHcloud : +#### Via l'espace client OVHcloud ![Apply your changes to the zone](images/deploy.png){.thumbnail} -#### Via l'API : +#### Via l'API OVHcloud > [!api] > @@ -258,11 +258,9 @@ Une fois que vous avez terminé de configurer les composants du service Load Bal |---|---| |serviceName|Votre ID de service Load Balancer| -### Basculement production/staging +### Changement de production ou de mise en scène -À ce stade, notre environnement initial est déployé et prêt à l'emploi. - -Maintenant, vous devez basculer vos front-ends d'une ferme de serveurs à une autre. +À ce stade, notre environnement initial est déployé et prêt à l'emploi. Maintenant, vous devez basculer vos front-ends d'une ferme de serveurs à une autre. Prenons notre scénario : @@ -277,11 +275,11 @@ Le **front-end blue** (id 70089) sera alors associé à la **Ferme B** (infrastr Le **front-end green** (id 70090) sera alors associé à la **Ferme A** (infrastructure A, nouveau développement, id 77212). -Voici le résultat attendu sur le Panneau de configuration OVHcloud après la mise à jour des front-ends et l'application de la nouvelle configuration : +Voici le résultat attendu dans l'espace client OVHcloud après la mise à jour des front-ends et l'application de la nouvelle configuration : ![Result after updating front-ends](images/switch.png){.thumbnail} -#### Via l'API : mise à jour des front-ends et application des modifications +#### Via l'API OVHcloud : mise à jour des front-ends et application des modifications > [!api] > @@ -305,7 +303,7 @@ Voici le résultat attendu sur le Panneau de configuration OVHcloud après la mi |frontendId|Votre ID de front-end de production|70090| |defaultFarmId|Votre ID de ferme de serveurs de développement|77212| -#### Pour appliquer vos modifications et basculer effectivement les environnements de production et de développement : +#### Pour appliquer vos modifications et basculer effectivement les environnements de production et de développement > [!api] > @@ -328,4 +326,4 @@ Une autre façon de consolider davantage votre infrastructure est de multiplier ## Aller plus loin -Échangez avec notre [communauté d'utilisateurs](/links/community). \ No newline at end of file +Échangez avec notre [communauté d'utilisateurs](/links/community). From 43cdf0a6ae017e96fd48bf57a982a13017ada5e3 Mon Sep 17 00:00:00 2001 From: Montrealhub <89825661+Jessica41@users.noreply.github.com> Date: Tue, 21 Oct 2025 19:26:54 -0400 Subject: [PATCH 12/23] first proof guide.en-gb.md --- .../load_balancer/case_smtp/guide.en-gb.md | 30 +++++++++---------- 1 file changed, 15 insertions(+), 15 deletions(-) diff --git a/pages/network/load_balancer/case_smtp/guide.en-gb.md b/pages/network/load_balancer/case_smtp/guide.en-gb.md index 3c10c918aeb..e905e73bc45 100644 --- a/pages/network/load_balancer/case_smtp/guide.en-gb.md +++ b/pages/network/load_balancer/case_smtp/guide.en-gb.md @@ -1,7 +1,7 @@ --- title: 'How to configure SMTP on a Load Balancer service' excerpt: 'Find out how to use SMTP with the OVHcloud Load Balancer' -updated: 2025-10-17 +updated: 2025-10-21 --- ## Objective @@ -32,7 +32,7 @@ In the Control Panel, you will see the features detailed below: ![OVHcloud Load Balancer service](images/iplb_service.png){.thumbnail} -Via the OVHcloud API, in the section: +Via the OVHcloud API, use the following call: > [!api] > @@ -43,9 +43,9 @@ For more information on the API features, you can refer to [the following guide] ### Add a server farm -A farm of TCP servers must be added to the service; this component manages traffic balancing across the servers. +A TCP server farm must be added to the service; this component manages traffic balancing across the servers. -#### Via the Control Panel +#### Via the OVHcloud Control Panel In the `Farms`{.action} tab for servers, click on the `+TCP/TLS`{.action} button. @@ -55,13 +55,13 @@ Optionally, you can add an SMTP probe on your farm. ![Add a server farm via the Control Panel](images/add_farm.png){.thumbnail} -Click `Add`{.action} once the fields are filled. +Click on `Add`{.action} once you have filled in the fields. Your server farm should appear in the list, in the `Farms`{.action} tab. ![Details of the server farm created](images/resume_farm.png){.thumbnail} -#### Via the API +#### Via the OVHcloud API - List of TCP server farms: @@ -102,7 +102,7 @@ Your server farm should appear in the list, in the `Farms`{.action} tab. A server must now be added to the server farm. -#### Via the Control Panel +#### Via the OVHcloud Control Panel In the `Farms`{.action} tab, select the farm you want to add a server to by clicking on the corresponding line. The list of servers already configured in the farm will appear beneath the list of farms, along with the `Add a server`{.action} button. Click this button to add a new server. @@ -115,13 +115,13 @@ The mandatory fields are the *IPv4 address*, *Status*, and *ProxyProtocol versio ![Add a server to a farm.](images/add_server.png){.thumbnail} -Click `Add`{.action} once the fields are filled. +Click on `Add`{.action} once you have filled in the fields. Your server should appear in the server list, in the `Farms`{.action} tab, just below the list of farms. ![Details of the server created.](images/resume_server.png){.thumbnail} -#### Via the API +#### Via the OVHcloud API - List of servers in the farm: @@ -162,7 +162,7 @@ Your server should appear in the server list, in the `Farms`{.action} tab, just A `front-end`{.action} must now be added to the service and connected to the server farm. The front-end is the component of your OVHcloud Load Balancer that exposes your service to the internet. -#### Via the Control Panel +#### Via the OVHcloud Control Panel Go to the `+ Front-ends`{.action} tab, and click `+TCP/TLS`{.action}. @@ -180,7 +180,7 @@ Your front-end must appear in the list, in the `Front-ends`{.action} tab. ![Details of the front-end created](images/resume_frontend.png){.thumbnail} -#### Via the API +#### Via the OVHcloud API - List of TCP front-ends: @@ -219,15 +219,15 @@ Your front-end must appear in the list, in the `Front-ends`{.action} tab. ### Apply the modifications -Modifications made to your OVHcloud Load Balancer must be *explicitly applied* in each of the zones configured for your service. They will only become visible to your users at this point. This process allows for complex configuration changes to be prepared and applied only when fully ready. +Modifications made to your OVHcloud Load Balancer must be **explicitly applied** in each of the zones configured for your service. They will only become visible to your users at this point. This process allows for complex configuration changes to be prepared and applied only when fully ready. If you have several zones, the same configuration must be applied to each. -#### Via the Control Panel +#### Via the OVHcloud Control Panel Go to the homepage for the OVHcloud Load Balancer, and click `Apply:Zone`{.action} for each of the zones concerned. -#### Via the API +#### Via the OVHcloud API - Refresh a zone: @@ -254,4 +254,4 @@ Upon completing these steps, you will have a functional Load Balancer service fo ## Go further -Join our [community of users](/links/community). \ No newline at end of file +Join our [community of users](/links/community). From 5f83d0ac9d11d15d4ebc42fd0f609843c2964528 Mon Sep 17 00:00:00 2001 From: Montrealhub <89825661+Jessica41@users.noreply.github.com> Date: Tue, 21 Oct 2025 19:38:56 -0400 Subject: [PATCH 13/23] first proofread guide.fr-fr.md --- pages/network/load_balancer/case_smtp/guide.fr-fr.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/pages/network/load_balancer/case_smtp/guide.fr-fr.md b/pages/network/load_balancer/case_smtp/guide.fr-fr.md index 74f45285703..51a449da24e 100644 --- a/pages/network/load_balancer/case_smtp/guide.fr-fr.md +++ b/pages/network/load_balancer/case_smtp/guide.fr-fr.md @@ -1,7 +1,7 @@ --- title: 'Comment configurer le SMTP sur un service Load Balancer' excerpt: 'Découvrez comment utiliser le SMTP avec le Load Balancer OVHcloud' -updated: 2025-10-17 +updated: 2025-10-21 --- ## Objectif @@ -29,7 +29,7 @@ Pour rappel, chaque protocole (HTTP, TCP et UDP) du service OVHcloud Load Balanc > > L'ordre de création des éléments est important. > En particulier, les fermes de serveurs doivent être configurées **avant** de pouvoir leur attacher des serveurs. -> +> Les fonctionnalités détaillées ci-dessous sont disponibles dans l'espace client OVHcloud : @@ -66,7 +66,7 @@ Votre ferme de serveurs devrait apparaître dans la liste, sous l'onglet `Fermes ![Détails de la ferme de serveurs créée](images/resume_farm.png){.thumbnail} -#### Depuis l'API OVHcloud +#### Depuis l'API OVHcloud - Liste des fermes de serveurs TCP : @@ -120,6 +120,7 @@ Les champs obligatoires sont l'*Adresse IPv4*, l'*État* et la *Version du Proxy > ![Ajout d'un serveur dans une ferme](images/add_server.png){.thumbnail} + ![Ajout d'un serveur dans une ferme](images/add_server_advance.png){.thumbnail} Cliquez sur le bouton `Ajouter`{.action} une fois les champs remplis. @@ -226,7 +227,7 @@ Votre *frontend* devrait apparaître dans la liste, sous l'onglet `Frontends`{.a ### Appliquer les modifications -Les modifications apportées à votre service OVHcloud Load Balancer doivent être *appliquées explicitement* dans chacune des zones configurées pour votre service. C'est seulement à ce moment qu'elles deviendront visibles pour vos visiteurs. Ce processus permet de préparer des changements de configuration complexes et de ne les appliquer qu'une fois la configuration entièrement prête. +Les modifications apportées à votre service OVHcloud Load Balancer doivent être **appliquées explicitement** dans chacune des zones configurées pour votre service. C'est seulement à ce moment qu'elles deviendront visibles pour vos visiteurs. Ce processus permet de préparer des changements de configuration complexes et de ne les appliquer qu'une fois la configuration entièrement prête. Si vous avez plusieurs zones, la même configuration devra être appliquée pour chacune de vos zones. @@ -261,4 +262,4 @@ Une fois toutes ces étapes terminées, vous devriez disposer d'un service de r ## Aller plus loin -Échangez avec notre [communauté d'utilisateurs](/links/community). \ No newline at end of file +Échangez avec notre [communauté d'utilisateurs](/links/community). From 70b977720a2ac6bed9e51c2a6a1acffb2273203b Mon Sep 17 00:00:00 2001 From: Montrealhub <89825661+Jessica41@users.noreply.github.com> Date: Tue, 21 Oct 2025 20:14:26 -0400 Subject: [PATCH 14/23] first proof guide.en-gb.md --- .../load_balancer/create_balancing/guide.en-gb.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/pages/network/load_balancer/create_balancing/guide.en-gb.md b/pages/network/load_balancer/create_balancing/guide.en-gb.md index 63331c2c3ff..ec0383a9b82 100644 --- a/pages/network/load_balancer/create_balancing/guide.en-gb.md +++ b/pages/network/load_balancer/create_balancing/guide.en-gb.md @@ -1,7 +1,7 @@ --- title: Load balancing methods excerpt: Discover the various load balancing algorithms available with the OVHcloud Load Balancer -updated: 2025-10-17 +updated: 2025-10-21 --- ## Objective @@ -32,21 +32,21 @@ For an overview of the OVHcloud Load Balancer service components, please refer t |**Source**|Uses a hash of the source IP address to consistently redirect the same client IP to the same server, provided the server remains operational.| |**URI**|Uses a hash of part or all of the URI path to consistently redirect identical URIs to the same server, provided the server remains operational. *(Applicable to HTTP/HTTPS farms only.)*| -### Modify a server farm’s load balancing method via the Control Panel +### Modify a server farm’s load balancing method via the OVHcloud Control Panel -- In the `Server farms`{.action} section (1), locate the desired farm. You can edit it by clicking the three dots on the right-hand side (2), then `Change`{.action}: +- In the `Server farms`{.action} section (1), locate the desired farm. You can edit it by clicking the three dots on the right-hand side (2), then `Change`{.action}. ![Modify a farm](images/server_cluster_change.png){.thumbnail} -In `Advanced settings`{.action}, modify the `Load balancing method`{.action}: +In `Advanced settings`{.action}, modify the `Load balancing method`{.action}. ![Modify a farm](images/distrib_mode_edit.png){.thumbnail} -Once your preferred method is selected, click `Update`{.action}, then click `Apply configuration`{.action} in the yellow banner that appears: +Once your preferred method is selected, click `Update`{.action}, then click `Apply configuration`{.action} in the yellow banner that appears. ![Apply configuration](images/apply_config.png){.thumbnail} -### Modify a server farm’s load balancing method via the API +### Modify a server farm’s load balancing method via the OVHcloud API The load balancing method is changed by updating the corresponding field within the server farm configuration. @@ -103,4 +103,4 @@ Use this call to edit the settings of a server farm given its ID. In this exampl ## Go further -Join our [community of users](/links/community). \ No newline at end of file +Join our [community of users](/links/community). From adacfd3a07057d81a18f550a6e9f682c82ac9fd3 Mon Sep 17 00:00:00 2001 From: Montrealhub <89825661+Jessica41@users.noreply.github.com> Date: Wed, 22 Oct 2025 12:29:40 -0400 Subject: [PATCH 15/23] first proof guide.fr-fr.md --- .../load_balancer/create_balancing/guide.fr-fr.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/pages/network/load_balancer/create_balancing/guide.fr-fr.md b/pages/network/load_balancer/create_balancing/guide.fr-fr.md index af304b13075..8f3b7f9aed3 100644 --- a/pages/network/load_balancer/create_balancing/guide.fr-fr.md +++ b/pages/network/load_balancer/create_balancing/guide.fr-fr.md @@ -1,7 +1,7 @@ --- title: Modes de répartition excerpt: Découvrez les différents modes de répartition de charge du Load Balancer OVHcloud -updated: 2025-10-17 +updated: 2025-10-21 --- ## Objectif @@ -32,9 +32,9 @@ Pour une vue d'ensemble des composants du service OVHcloud Load Balancer, consul |**Source**|Utilise une fonction de *hachage* sur l'adresse IP source pour rediriger systématiquement la même IP cliente vers le même serveur, tant que celui-ci reste opérationnel.| |**URI**|Utilise une fonction de *hachage* sur une partie ou la totalité de l'URI pour rediriger systématiquement les URI identiques vers le même serveur, tant que celui-ci reste opérationnel. *(Applicable uniquement aux fermes HTTP/HTTPS.)*| -### Modifier l'algorithme de répartition de charge d'une ferme via l'espace client +### Modifier l'algorithme de répartition de charge d'une ferme via l'espace client OVHcloud -Dans la section `Fermes de serveur`{.action}, vous verrez les fermes actuellement créées. Il vous suffit d'éditer l'une d'entre elles en cliquant sur les trois points à droite puis `Modifier`{.action} : +Dans la section `Fermes de serveur`{.action}, vous verrez les fermes actuellement créées. Il vous suffit d'éditer l'une d'entre elles en cliquant sur les trois points à droite puis sur `Modifier`{.action} : ![Modification d'une ferme](images/server_cluster_change.png){.thumbnail} @@ -52,7 +52,7 @@ La modification de l'algorithme de répartition s'effectue en éditant le champ #### Voir le détail d'une ferme -Cet appel permet de consulter le détail d'une ferme en connaissant son identifiant. Dans cet exemple, nous travaillons sur une ferme HTTP : +Cet appel API permet de consulter le détail d'une ferme en connaissant son identifiant. Dans cet exemple, nous travaillons sur une ferme HTTP : > [!api] > @@ -76,7 +76,7 @@ Cet appel permet de consulter le détail d'une ferme en connaissant son identifi #### Modifier l'algorithme de répartition de charge d'une ferme -Cet appel permet de modifier la configuration d'une ferme en connaissant son identifiant. Dans cet exemple, nous travaillons sur une ferme HTTP. Pour modifier le mode de répartition, le champ `BackendHttp.balance` doit être mis à jour avec un algorithme disponible : +Cet appel API permet de modifier la configuration d'une ferme en connaissant son identifiant. Dans cet exemple, nous travaillons sur une ferme HTTP. Pour modifier le mode de répartition, le champ `BackendHttp.balance` doit être mis à jour avec un algorithme disponible : > [!api] > @@ -103,4 +103,4 @@ Cet appel permet de modifier la configuration d'une ferme en connaissant son ide ## Aller plus loin -Échangez avec notre [communauté d'utilisateurs](/links/community). \ No newline at end of file +Échangez avec notre [communauté d'utilisateurs](/links/community). From cabf3111b2c5080d91fa6833711a8ffdbba846fc Mon Sep 17 00:00:00 2001 From: Montrealhub <89825661+Jessica41@users.noreply.github.com> Date: Wed, 22 Oct 2025 13:23:23 -0400 Subject: [PATCH 16/23] first proof guide.en-gb.md --- .../order_freecertificate/guide.en-gb.md | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/pages/network/load_balancer/order_freecertificate/guide.en-gb.md b/pages/network/load_balancer/order_freecertificate/guide.en-gb.md index d65968df4bd..de331e8cd29 100644 --- a/pages/network/load_balancer/order_freecertificate/guide.en-gb.md +++ b/pages/network/load_balancer/order_freecertificate/guide.en-gb.md @@ -1,7 +1,7 @@ --- title: Order a free SSL certificate excerpt: Order a free SSL certificate for your web services behind a Load Balancer -updated: 2025-09-26 +updated: 2025-10-22 --- ## Objective @@ -49,7 +49,7 @@ In the `SSL Certificates` section of your Control Panel, click the `Order SSL Ce In the `Tasks`{.action} section of your Control Panel, the tasks related to ordering a free SSL Certificate are of the type `orderFreeCertificate`. -### Via the API +### Via the OVHcloud API #### Configuring the frontend for SSL termination @@ -60,7 +60,7 @@ In the API, the SSL termination is specified by the `ssl` boolean. To enable SSL > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/frontend > -Then apply the changes : +Then apply the changes: > [!api] > @@ -69,7 +69,8 @@ Then apply the changes : #### Order the free SSL certificate -In the API, the command is as follows : +In the API, the call is as follows: + > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/freeCertificate @@ -81,14 +82,14 @@ For the order to be finalized, the chosen domain name must point to your OVHclou - Returning the task list -You can specify the action type `orderFreeCertificate` to refine the search. +You can specify the action type `orderFreeCertificate` to refine the search: > [!api] > > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/task > -- Returning the status of a particular task +- Returning the status of a particular task: > [!api] > From a0236f87d8bf0e78b599b7514ce3cab0027b1b3b Mon Sep 17 00:00:00 2001 From: Montrealhub <89825661+Jessica41@users.noreply.github.com> Date: Wed, 22 Oct 2025 14:52:06 -0400 Subject: [PATCH 17/23] first proof guide.fr-fr.md --- .../network/load_balancer/order_freecertificate/guide.fr-fr.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/network/load_balancer/order_freecertificate/guide.fr-fr.md b/pages/network/load_balancer/order_freecertificate/guide.fr-fr.md index dc3da1db0a5..5d253388702 100644 --- a/pages/network/load_balancer/order_freecertificate/guide.fr-fr.md +++ b/pages/network/load_balancer/order_freecertificate/guide.fr-fr.md @@ -1,7 +1,7 @@ --- title: "Commande d'un certificat SSL gratuit" excerpt: Commander un certificat SSL gratuit pour vos services web derrière un Load Balancer -updated: 2025-09-26 +updated: 2025-10-22 --- ## Objectif From a4c7c113fd140fe9f5c2fc2e9b72e28a8e45dbe9 Mon Sep 17 00:00:00 2001 From: jessica Date: Thu, 23 Oct 2025 17:27:56 -0400 Subject: [PATCH 18/23] duplos and fixes --- .../order_freecertificate/guide.en-asia.md | 87 +++++++++++------- .../order_freecertificate/guide.en-au.md | 87 +++++++++++------- .../order_freecertificate/guide.en-ca.md | 87 +++++++++++------- .../order_freecertificate/guide.en-gb.md | 6 +- .../order_freecertificate/guide.en-sg.md | 87 +++++++++++------- .../order_freecertificate/guide.en-us.md | 89 ++++++++++++------- .../order_freecertificate/guide.fr-ca.md | 89 ++++++++++++------- .../order_freecertificate/guide.fr-fr.md | 4 +- 8 files changed, 336 insertions(+), 200 deletions(-) diff --git a/pages/network/load_balancer/order_freecertificate/guide.en-asia.md b/pages/network/load_balancer/order_freecertificate/guide.en-asia.md index 5b10f7b5a52..0dc26599f11 100644 --- a/pages/network/load_balancer/order_freecertificate/guide.en-asia.md +++ b/pages/network/load_balancer/order_freecertificate/guide.en-asia.md @@ -1,80 +1,103 @@ --- title: Order a free SSL certificate -universe: cloud excerpt: Order a free SSL certificate for your web services behind a Load Balancer -updated: 2022-03-29 +updated: 2025-10-23 --- -## Presentation -The OVH Load Balancer service can be configured to support SSL termination.. +## Objective -The purpose of SSL termination is to decrypt the incoming encrypted stream before forwarding it to the appropriate service (web server for example). +The OVHcloud Load Balancer service can be configured to support SSL termination. -SSL termination has a cost for the service that manages it. Rather than letting your servers do it, it is possible to configure your OVH Load Balancer service to do it. +The purpose of SSL termination is to decrypt the incoming encrypted stream before forwarding it to the appropriate service, such as a web server. -Moreover, all your certificates are centralized in one place and their maintenance is easier. +Handling SSL termination on the Load Balancer reduces the computational load on your backend servers and centralizes certificate management. This makes maintenance and security updates easier. -## Configuring the frontend for SSL termination -The first thing to do is to configure your frontend to handle SSL termination. +**Discover how to order a free SSL certificate via the OVHcloud Control Panel or the API.** -### Via the Manager -In the `Frontends` section of your Manager, click on the `Add Frontend`{.action} button to create a new frontend. An edit window will appear, select the `HTTPS` protocol. You will also need to fill in the `Default Close` or `HTTPS Redirection` field in the advanced settings.. +## Requirements + +- You must have an [OVHcloud Load balancer](/links/network/load-balancer) in your OVHcloud account. +- You must be logged in to the [OVHcloud Control Panel](/links/manager). + +## Instructions + +### Via the OVHcloud Control Panel + +#### Configure the frontend for SSL termination + +To enable SSL termination, you must first configure your frontend. + +You can configure your SSL termination from the [OVHcloud Control Panel](/links/manager) in the `Bare Metal Cloud`{.action} section, then `Load Balancer`{.action}. + +After selecting the Load Balancer you wish to modify, create a new frontend or edit an existing one. + +In the `Frontends`{.action} section, click on the `Add Frontend`{.action} button to create a new frontend.
+In the configuration window that opens, select the `HTTPS` protocol. Then, select the `Default server cluster`.
+Finally, open the advanced settings and fill in the `HTTPS Redirection` field. ![Configuring the SSL termination of a Frontend](images/enable_ssl_terminaison.png){.thumbnail} -Once the frontend has been created, you will be prompted to `Apply configuration`{.action} to apply your changes to the relevant area. +Once the frontend has been created, a banner will appear prompting you to `Apply the configuration` to deploy your changes in the appropriate zone. + +#### Order the free SSL certificate + +In the `SSL Certificates` section of your Control Panel, click the `Order SSL Certificate`{.action} button to create a new one. An edit window will appear with an `FQDN` field to be filled in. -### Via API -In the API, the SSL termination is specified by the ssl boolean: (Don't forget to set defaultFarmId or redirectLocation) +![Add a free SSL certificate](images/iplb-order-ssl.png){.thumbnail} + +#### Follow-up of the order + +In the `Tasks`{.action} section of your Control Panel, the tasks related to ordering a free SSL Certificate are of the type `orderFreeCertificate`. + +### Via the OVHcloud API + +#### Configuring the frontend for SSL termination + +In the API, the SSL termination is specified by the `ssl` boolean. To enable SSL termination, set this parameter to `true`, then set the `defaultFarmId` or `redirectLocation` to the corresponding values. > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/frontend > -Then apply the changes : +Then apply the changes: > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh > -## Order the free SSL certificate +#### Order the free SSL certificate -### Via the Manager -In the `SSL Certificates` section of your Manager, click the `Order SSL Certificate`{.action} button to create a new one. An edit window will appear with an `FQDN` field to be filled in. - -![Ajouter un certificate SSL gratuit](images/add_freecertificate.png){.thumbnail} - -### Via API -In the API, the command is as follows. For the order to be finalized, the chosen domain name must point to your OVH Load Balancer service. +In the API, the call is as follows: > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/freeCertificate > -## Follow-up of the order +For the order to be finalized, the chosen domain name must point to your OVHcloud Load Balancer service. -### Via the Manager -In the `Tasks`{.action} section of your Manager, the tasks related to ordering a free SSL Certificate are of the type `orderFreeCertificate`. +#### Follow-up of the order -### Via API +- Returning the task list -#### Return to task list -You can specify the action type orderFreeCertificate to refine the search. +You can specify the action type `orderFreeCertificate` to refine the search: > [!api] > > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/task > -#### Returning the status of a particular stain +- Returning the status of a particular task: > [!api] > > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/task/{id} > -## Delivery of the free SSL certificate -Once the order is complete, the SSL Certificate is automatically installed on your OVH Load Balancer service.. +Once the order is complete, the SSL Certificate is automatically installed on your OVHcloud Load Balancer service. + +## Go further + +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/order_freecertificate/guide.en-au.md b/pages/network/load_balancer/order_freecertificate/guide.en-au.md index 5b10f7b5a52..0dc26599f11 100644 --- a/pages/network/load_balancer/order_freecertificate/guide.en-au.md +++ b/pages/network/load_balancer/order_freecertificate/guide.en-au.md @@ -1,80 +1,103 @@ --- title: Order a free SSL certificate -universe: cloud excerpt: Order a free SSL certificate for your web services behind a Load Balancer -updated: 2022-03-29 +updated: 2025-10-23 --- -## Presentation -The OVH Load Balancer service can be configured to support SSL termination.. +## Objective -The purpose of SSL termination is to decrypt the incoming encrypted stream before forwarding it to the appropriate service (web server for example). +The OVHcloud Load Balancer service can be configured to support SSL termination. -SSL termination has a cost for the service that manages it. Rather than letting your servers do it, it is possible to configure your OVH Load Balancer service to do it. +The purpose of SSL termination is to decrypt the incoming encrypted stream before forwarding it to the appropriate service, such as a web server. -Moreover, all your certificates are centralized in one place and their maintenance is easier. +Handling SSL termination on the Load Balancer reduces the computational load on your backend servers and centralizes certificate management. This makes maintenance and security updates easier. -## Configuring the frontend for SSL termination -The first thing to do is to configure your frontend to handle SSL termination. +**Discover how to order a free SSL certificate via the OVHcloud Control Panel or the API.** -### Via the Manager -In the `Frontends` section of your Manager, click on the `Add Frontend`{.action} button to create a new frontend. An edit window will appear, select the `HTTPS` protocol. You will also need to fill in the `Default Close` or `HTTPS Redirection` field in the advanced settings.. +## Requirements + +- You must have an [OVHcloud Load balancer](/links/network/load-balancer) in your OVHcloud account. +- You must be logged in to the [OVHcloud Control Panel](/links/manager). + +## Instructions + +### Via the OVHcloud Control Panel + +#### Configure the frontend for SSL termination + +To enable SSL termination, you must first configure your frontend. + +You can configure your SSL termination from the [OVHcloud Control Panel](/links/manager) in the `Bare Metal Cloud`{.action} section, then `Load Balancer`{.action}. + +After selecting the Load Balancer you wish to modify, create a new frontend or edit an existing one. + +In the `Frontends`{.action} section, click on the `Add Frontend`{.action} button to create a new frontend.
+In the configuration window that opens, select the `HTTPS` protocol. Then, select the `Default server cluster`.
+Finally, open the advanced settings and fill in the `HTTPS Redirection` field. ![Configuring the SSL termination of a Frontend](images/enable_ssl_terminaison.png){.thumbnail} -Once the frontend has been created, you will be prompted to `Apply configuration`{.action} to apply your changes to the relevant area. +Once the frontend has been created, a banner will appear prompting you to `Apply the configuration` to deploy your changes in the appropriate zone. + +#### Order the free SSL certificate + +In the `SSL Certificates` section of your Control Panel, click the `Order SSL Certificate`{.action} button to create a new one. An edit window will appear with an `FQDN` field to be filled in. -### Via API -In the API, the SSL termination is specified by the ssl boolean: (Don't forget to set defaultFarmId or redirectLocation) +![Add a free SSL certificate](images/iplb-order-ssl.png){.thumbnail} + +#### Follow-up of the order + +In the `Tasks`{.action} section of your Control Panel, the tasks related to ordering a free SSL Certificate are of the type `orderFreeCertificate`. + +### Via the OVHcloud API + +#### Configuring the frontend for SSL termination + +In the API, the SSL termination is specified by the `ssl` boolean. To enable SSL termination, set this parameter to `true`, then set the `defaultFarmId` or `redirectLocation` to the corresponding values. > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/frontend > -Then apply the changes : +Then apply the changes: > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh > -## Order the free SSL certificate +#### Order the free SSL certificate -### Via the Manager -In the `SSL Certificates` section of your Manager, click the `Order SSL Certificate`{.action} button to create a new one. An edit window will appear with an `FQDN` field to be filled in. - -![Ajouter un certificate SSL gratuit](images/add_freecertificate.png){.thumbnail} - -### Via API -In the API, the command is as follows. For the order to be finalized, the chosen domain name must point to your OVH Load Balancer service. +In the API, the call is as follows: > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/freeCertificate > -## Follow-up of the order +For the order to be finalized, the chosen domain name must point to your OVHcloud Load Balancer service. -### Via the Manager -In the `Tasks`{.action} section of your Manager, the tasks related to ordering a free SSL Certificate are of the type `orderFreeCertificate`. +#### Follow-up of the order -### Via API +- Returning the task list -#### Return to task list -You can specify the action type orderFreeCertificate to refine the search. +You can specify the action type `orderFreeCertificate` to refine the search: > [!api] > > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/task > -#### Returning the status of a particular stain +- Returning the status of a particular task: > [!api] > > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/task/{id} > -## Delivery of the free SSL certificate -Once the order is complete, the SSL Certificate is automatically installed on your OVH Load Balancer service.. +Once the order is complete, the SSL Certificate is automatically installed on your OVHcloud Load Balancer service. + +## Go further + +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/order_freecertificate/guide.en-ca.md b/pages/network/load_balancer/order_freecertificate/guide.en-ca.md index 1a7978f30a2..0dc26599f11 100644 --- a/pages/network/load_balancer/order_freecertificate/guide.en-ca.md +++ b/pages/network/load_balancer/order_freecertificate/guide.en-ca.md @@ -1,80 +1,103 @@ --- title: Order a free SSL certificate -universe: cloud excerpt: Order a free SSL certificate for your web services behind a Load Balancer -updated: 2022-03-29 +updated: 2025-10-23 --- -## Presentation -The OVH Load Balancer service can be configured to support SSL termination.. +## Objective -The purpose of SSL termination is to decrypt the incoming encrypted stream before forwarding it to the appropriate service (web server for example). +The OVHcloud Load Balancer service can be configured to support SSL termination. -SSL termination has a cost for the service that manages it. Rather than letting your servers do it, it is possible to configure your OVH Load Balancer service to do it. +The purpose of SSL termination is to decrypt the incoming encrypted stream before forwarding it to the appropriate service, such as a web server. -Moreover, all your certificates are centralized in one place and their maintenance is easier. +Handling SSL termination on the Load Balancer reduces the computational load on your backend servers and centralizes certificate management. This makes maintenance and security updates easier. -## Configuring the frontend for SSL termination -The first thing to do is to configure your frontend to handle SSL termination. +**Discover how to order a free SSL certificate via the OVHcloud Control Panel or the API.** -### Via the Manager -In the `Frontends` section of your Manager, click on the `Add Frontend`{.action} button to create a new frontend. An edit window will appear, select the `HTTPS` protocol. You will also need to fill in the `Default Close` or `HTTPS Redirection` field in the advanced settings.. +## Requirements + +- You must have an [OVHcloud Load balancer](/links/network/load-balancer) in your OVHcloud account. +- You must be logged in to the [OVHcloud Control Panel](/links/manager). + +## Instructions + +### Via the OVHcloud Control Panel + +#### Configure the frontend for SSL termination + +To enable SSL termination, you must first configure your frontend. + +You can configure your SSL termination from the [OVHcloud Control Panel](/links/manager) in the `Bare Metal Cloud`{.action} section, then `Load Balancer`{.action}. + +After selecting the Load Balancer you wish to modify, create a new frontend or edit an existing one. + +In the `Frontends`{.action} section, click on the `Add Frontend`{.action} button to create a new frontend.
+In the configuration window that opens, select the `HTTPS` protocol. Then, select the `Default server cluster`.
+Finally, open the advanced settings and fill in the `HTTPS Redirection` field. ![Configuring the SSL termination of a Frontend](images/enable_ssl_terminaison.png){.thumbnail} -Once the frontend has been created, you will be prompted to `Apply configuration`{.action} to apply your changes to the relevant area. +Once the frontend has been created, a banner will appear prompting you to `Apply the configuration` to deploy your changes in the appropriate zone. + +#### Order the free SSL certificate -### Via API -In the API, the SSL termination is specified by the ssl boolean: (Don't forget to set defaultFarmId or redirectLocation) +In the `SSL Certificates` section of your Control Panel, click the `Order SSL Certificate`{.action} button to create a new one. An edit window will appear with an `FQDN` field to be filled in. + +![Add a free SSL certificate](images/iplb-order-ssl.png){.thumbnail} + +#### Follow-up of the order + +In the `Tasks`{.action} section of your Control Panel, the tasks related to ordering a free SSL Certificate are of the type `orderFreeCertificate`. + +### Via the OVHcloud API + +#### Configuring the frontend for SSL termination + +In the API, the SSL termination is specified by the `ssl` boolean. To enable SSL termination, set this parameter to `true`, then set the `defaultFarmId` or `redirectLocation` to the corresponding values. > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/frontend > -Then apply the changes : +Then apply the changes: > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh > -## Order the free SSL certificate +#### Order the free SSL certificate -### Via the Manager -In the `SSL Certificates` section of your Manager, click the `Order SSL Certificate`{.action} button to create a new one. An edit window will appear with an `FQDN` field to be filled in. - -![Add a free SSL certificate](images/iplb-order-ssl.png){.thumbnail} - -### Via API -In the API, the command is as follows. For the order to be finalized, the chosen domain name must point to your OVH Load Balancer service. +In the API, the call is as follows: > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/freeCertificate > -## Follow-up of the order +For the order to be finalized, the chosen domain name must point to your OVHcloud Load Balancer service. -### Via the Manager -In the `Tasks`{.action} section of your Manager, the tasks related to ordering a free SSL Certificate are of the type `orderFreeCertificate`. +#### Follow-up of the order -### Via API +- Returning the task list -#### Return to task list -You can specify the action type orderFreeCertificate to refine the search. +You can specify the action type `orderFreeCertificate` to refine the search: > [!api] > > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/task > -#### Returning the status of a particular stain +- Returning the status of a particular task: > [!api] > > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/task/{id} > -## Delivery of the free SSL certificate -Once the order is complete, the SSL Certificate is automatically installed on your OVH Load Balancer service.. +Once the order is complete, the SSL Certificate is automatically installed on your OVHcloud Load Balancer service. + +## Go further + +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/order_freecertificate/guide.en-gb.md b/pages/network/load_balancer/order_freecertificate/guide.en-gb.md index de331e8cd29..0dc26599f11 100644 --- a/pages/network/load_balancer/order_freecertificate/guide.en-gb.md +++ b/pages/network/load_balancer/order_freecertificate/guide.en-gb.md @@ -1,7 +1,7 @@ --- title: Order a free SSL certificate excerpt: Order a free SSL certificate for your web services behind a Load Balancer -updated: 2025-10-22 +updated: 2025-10-23 --- ## Objective @@ -37,7 +37,7 @@ Finally, open the advanced settings and fill in the `HTTPS Redirection` field. ![Configuring the SSL termination of a Frontend](images/enable_ssl_terminaison.png){.thumbnail} -Once the frontend has been created, a banner will appear prompting you to `Apply configuration` to deploy your changes in the appropriate zone. +Once the frontend has been created, a banner will appear prompting you to `Apply the configuration` to deploy your changes in the appropriate zone. #### Order the free SSL certificate @@ -100,4 +100,4 @@ Once the order is complete, the SSL Certificate is automatically installed on yo ## Go further -Join our [community of users](/links/community). +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/order_freecertificate/guide.en-sg.md b/pages/network/load_balancer/order_freecertificate/guide.en-sg.md index 5b10f7b5a52..0dc26599f11 100644 --- a/pages/network/load_balancer/order_freecertificate/guide.en-sg.md +++ b/pages/network/load_balancer/order_freecertificate/guide.en-sg.md @@ -1,80 +1,103 @@ --- title: Order a free SSL certificate -universe: cloud excerpt: Order a free SSL certificate for your web services behind a Load Balancer -updated: 2022-03-29 +updated: 2025-10-23 --- -## Presentation -The OVH Load Balancer service can be configured to support SSL termination.. +## Objective -The purpose of SSL termination is to decrypt the incoming encrypted stream before forwarding it to the appropriate service (web server for example). +The OVHcloud Load Balancer service can be configured to support SSL termination. -SSL termination has a cost for the service that manages it. Rather than letting your servers do it, it is possible to configure your OVH Load Balancer service to do it. +The purpose of SSL termination is to decrypt the incoming encrypted stream before forwarding it to the appropriate service, such as a web server. -Moreover, all your certificates are centralized in one place and their maintenance is easier. +Handling SSL termination on the Load Balancer reduces the computational load on your backend servers and centralizes certificate management. This makes maintenance and security updates easier. -## Configuring the frontend for SSL termination -The first thing to do is to configure your frontend to handle SSL termination. +**Discover how to order a free SSL certificate via the OVHcloud Control Panel or the API.** -### Via the Manager -In the `Frontends` section of your Manager, click on the `Add Frontend`{.action} button to create a new frontend. An edit window will appear, select the `HTTPS` protocol. You will also need to fill in the `Default Close` or `HTTPS Redirection` field in the advanced settings.. +## Requirements + +- You must have an [OVHcloud Load balancer](/links/network/load-balancer) in your OVHcloud account. +- You must be logged in to the [OVHcloud Control Panel](/links/manager). + +## Instructions + +### Via the OVHcloud Control Panel + +#### Configure the frontend for SSL termination + +To enable SSL termination, you must first configure your frontend. + +You can configure your SSL termination from the [OVHcloud Control Panel](/links/manager) in the `Bare Metal Cloud`{.action} section, then `Load Balancer`{.action}. + +After selecting the Load Balancer you wish to modify, create a new frontend or edit an existing one. + +In the `Frontends`{.action} section, click on the `Add Frontend`{.action} button to create a new frontend.
+In the configuration window that opens, select the `HTTPS` protocol. Then, select the `Default server cluster`.
+Finally, open the advanced settings and fill in the `HTTPS Redirection` field. ![Configuring the SSL termination of a Frontend](images/enable_ssl_terminaison.png){.thumbnail} -Once the frontend has been created, you will be prompted to `Apply configuration`{.action} to apply your changes to the relevant area. +Once the frontend has been created, a banner will appear prompting you to `Apply the configuration` to deploy your changes in the appropriate zone. + +#### Order the free SSL certificate + +In the `SSL Certificates` section of your Control Panel, click the `Order SSL Certificate`{.action} button to create a new one. An edit window will appear with an `FQDN` field to be filled in. -### Via API -In the API, the SSL termination is specified by the ssl boolean: (Don't forget to set defaultFarmId or redirectLocation) +![Add a free SSL certificate](images/iplb-order-ssl.png){.thumbnail} + +#### Follow-up of the order + +In the `Tasks`{.action} section of your Control Panel, the tasks related to ordering a free SSL Certificate are of the type `orderFreeCertificate`. + +### Via the OVHcloud API + +#### Configuring the frontend for SSL termination + +In the API, the SSL termination is specified by the `ssl` boolean. To enable SSL termination, set this parameter to `true`, then set the `defaultFarmId` or `redirectLocation` to the corresponding values. > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/frontend > -Then apply the changes : +Then apply the changes: > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh > -## Order the free SSL certificate +#### Order the free SSL certificate -### Via the Manager -In the `SSL Certificates` section of your Manager, click the `Order SSL Certificate`{.action} button to create a new one. An edit window will appear with an `FQDN` field to be filled in. - -![Ajouter un certificate SSL gratuit](images/add_freecertificate.png){.thumbnail} - -### Via API -In the API, the command is as follows. For the order to be finalized, the chosen domain name must point to your OVH Load Balancer service. +In the API, the call is as follows: > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/freeCertificate > -## Follow-up of the order +For the order to be finalized, the chosen domain name must point to your OVHcloud Load Balancer service. -### Via the Manager -In the `Tasks`{.action} section of your Manager, the tasks related to ordering a free SSL Certificate are of the type `orderFreeCertificate`. +#### Follow-up of the order -### Via API +- Returning the task list -#### Return to task list -You can specify the action type orderFreeCertificate to refine the search. +You can specify the action type `orderFreeCertificate` to refine the search: > [!api] > > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/task > -#### Returning the status of a particular stain +- Returning the status of a particular task: > [!api] > > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/task/{id} > -## Delivery of the free SSL certificate -Once the order is complete, the SSL Certificate is automatically installed on your OVH Load Balancer service.. +Once the order is complete, the SSL Certificate is automatically installed on your OVHcloud Load Balancer service. + +## Go further + +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/order_freecertificate/guide.en-us.md b/pages/network/load_balancer/order_freecertificate/guide.en-us.md index 8d352ccb803..0dc26599f11 100644 --- a/pages/network/load_balancer/order_freecertificate/guide.en-us.md +++ b/pages/network/load_balancer/order_freecertificate/guide.en-us.md @@ -1,80 +1,103 @@ --- title: Order a free SSL certificate -universe: cloud excerpt: Order a free SSL certificate for your web services behind a Load Balancer -updated: 2022-03-29 +updated: 2025-10-23 --- -## Presentation -The OVH Load Balancer service can be configured to support SSL termination.. +## Objective -The purpose of SSL termination is to decrypt the incoming encrypted stream before forwarding it to the appropriate service (web server for example). +The OVHcloud Load Balancer service can be configured to support SSL termination. -SSL termination has a cost for the service that manages it. Rather than letting your servers do it, it is possible to configure your OVH Load Balancer service to do it. +The purpose of SSL termination is to decrypt the incoming encrypted stream before forwarding it to the appropriate service, such as a web server. -Moreover, all your certificates are centralized in one place and their maintenance is easier. +Handling SSL termination on the Load Balancer reduces the computational load on your backend servers and centralizes certificate management. This makes maintenance and security updates easier. -## Configuring the frontend for SSL termination -The first thing to do is to configure your frontend to handle SSL termination. +**Discover how to order a free SSL certificate via the OVHcloud Control Panel or the API.** -### Via the Manager -In the `Frontends` section of your Manager, click on the `Add Frontend`{.action} button to create a new frontend. An edit window will appear, select the `HTTPS` protocol. You will also need to fill in the `Default Close` or `HTTPS Redirection` field in the advanced settings.. +## Requirements -![Configuring the SSL termination of a Frontend](images/iplb-add-front-end.png){.thumbnail} +- You must have an [OVHcloud Load balancer](/links/network/load-balancer) in your OVHcloud account. +- You must be logged in to the [OVHcloud Control Panel](/links/manager). -Once the frontend has been created, you will be prompted to `Apply configuration`{.action} to apply your changes to the relevant area. +## Instructions -### Via API -In the API, the SSL termination is specified by the ssl boolean: (Don't forget to set defaultFarmId or redirectLocation) +### Via the OVHcloud Control Panel + +#### Configure the frontend for SSL termination + +To enable SSL termination, you must first configure your frontend. + +You can configure your SSL termination from the [OVHcloud Control Panel](/links/manager) in the `Bare Metal Cloud`{.action} section, then `Load Balancer`{.action}. + +After selecting the Load Balancer you wish to modify, create a new frontend or edit an existing one. + +In the `Frontends`{.action} section, click on the `Add Frontend`{.action} button to create a new frontend.
+In the configuration window that opens, select the `HTTPS` protocol. Then, select the `Default server cluster`.
+Finally, open the advanced settings and fill in the `HTTPS Redirection` field. + +![Configuring the SSL termination of a Frontend](images/enable_ssl_terminaison.png){.thumbnail} + +Once the frontend has been created, a banner will appear prompting you to `Apply the configuration` to deploy your changes in the appropriate zone. + +#### Order the free SSL certificate + +In the `SSL Certificates` section of your Control Panel, click the `Order SSL Certificate`{.action} button to create a new one. An edit window will appear with an `FQDN` field to be filled in. + +![Add a free SSL certificate](images/iplb-order-ssl.png){.thumbnail} + +#### Follow-up of the order + +In the `Tasks`{.action} section of your Control Panel, the tasks related to ordering a free SSL Certificate are of the type `orderFreeCertificate`. + +### Via the OVHcloud API + +#### Configuring the frontend for SSL termination + +In the API, the SSL termination is specified by the `ssl` boolean. To enable SSL termination, set this parameter to `true`, then set the `defaultFarmId` or `redirectLocation` to the corresponding values. > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/frontend > -Then apply the changes : +Then apply the changes: > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh > -## Order the free SSL certificate +#### Order the free SSL certificate -### Via the Manager -In the `SSL Certificates` section of your Manager, click the `Order SSL Certificate`{.action} button to create a new one. An edit window will appear with an `FQDN` field to be filled in. - -![Ajouter un certificate SSL gratuit](images/iplb-order-ssl.png){.thumbnail} - -### Via API -In the API, the command is as follows. For the order to be finalized, the chosen domain name must point to your OVH Load Balancer service. +In the API, the call is as follows: > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/freeCertificate > -## Follow-up of the order +For the order to be finalized, the chosen domain name must point to your OVHcloud Load Balancer service. -### Via the Manager -In the `Tasks`{.action} section of your Manager, the tasks related to ordering a free SSL Certificate are of the type `orderFreeCertificate`. +#### Follow-up of the order -### Via API +- Returning the task list -#### Return to task list -You can specify the action type orderFreeCertificate to refine the search. +You can specify the action type `orderFreeCertificate` to refine the search: > [!api] > > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/task > -#### Returning the status of a particular stain +- Returning the status of a particular task: > [!api] > > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/task/{id} > -## Delivery of the free SSL certificate -Once the order is complete, the SSL Certificate is automatically installed on your OVH Load Balancer service.. +Once the order is complete, the SSL Certificate is automatically installed on your OVHcloud Load Balancer service. + +## Go further + +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/order_freecertificate/guide.fr-ca.md b/pages/network/load_balancer/order_freecertificate/guide.fr-ca.md index aa812fc8802..9f4c85e5c03 100644 --- a/pages/network/load_balancer/order_freecertificate/guide.fr-ca.md +++ b/pages/network/load_balancer/order_freecertificate/guide.fr-ca.md @@ -1,80 +1,101 @@ --- -title: Commander un certificat SSL gratuit -universe: cloud +title: "Commande d'un certificat SSL gratuit" excerpt: Commander un certificat SSL gratuit pour vos services web derrière un Load Balancer -updated: 2022-03-29 +updated: 2025-10-23 --- -## Presentation -Le service OVH Load Balancer peut être configuré pour prendre en charge la terminaison SSL. +## Objectif -La terminaison SSL a pour but de déchiffrer le flux chiffré entrant avant de le faire suivre vers le service approprié (Serveur web par exemple). +Le service OVHcloud Load Balancer peut être configuré pour prendre en charge la terminaison SSL. -La terminaison SSL a un coût pour le service qui le gère. Plutôt que de laisser vos serveurs la faire, il est possible de configurer votre service OVH Load Balancer pour la faire. +La terminaison SSL a pour but de déchiffrer le flux chiffré entrant avant de le faire suivre vers le service approprié, tel qu'un serveur web. -De plus, tous vos certificats sont ainsi centralisés au même endroit et leur maintenance s'en trouve facilitée. +Le traitement de la terminaison SSL sur le Load Balancer réduit la charge de calcul sur vos serveurs backend et centralise la gestion des certificats. Cela facilite la maintenance et les mises à jour de sécurité. -## Configurer le frontend pour la terminaison SSL -La première chose à faire est de configurer votre frontend pour gérer la terminaison SSL. +**Découvrez comment commander un certificat SSL gratuit depuis votre espace client OVHcloud ou via l'API OVHcloud.** -### Via le Manager -Dans la section `Frontends` de votre Manager, cliquez sur le bouton `Ajouter un frontend`{.action} pour en créer un nouveau. Une fenêtre d'édition apparait alors, selectionnez le protocole `HTTPS`. Il faudra aussi renseigner le champ `Ferme par défaut` ou `Redirection HTTP` dans les paramètres avancés. +## Prérequis -![Configuration la terminaison SSL d'un Frontend](images/iplb-add-front-end.png){.thumbnail} +- Posséder une offre [OVHcloud Load balancer](/links/network/load-balancer) dans votre compte OVHcloud. +- Être connecté à votre [espace client OVHcloud](/links/manager) -Une fois le frontend créé, il vous sera proposé d'`Appliquer la configuration`{.action} pour appliquer vos changements dans la zone concernée. +## En pratique -### Via l'API -Dans l'API, la terminaison SSL est spécifiée par le booléen ssl : (N'oubliez pas de renseigner defaultFarmId ou redirectLocation) +### Depuis l'espace client OVHcloud + +La première étape est de configurer votre frontend pour gérer la terminaison SSL. + +Vous pouvez configurer votre terminaison SSL depuis l'[espace client OVHcloud](/links/manager) dans la partie `Bare Metal Cloud`{.action} puis `Load Balancer`{.action}. + +Après avoir sélectionné le Load Balancer que vous souhaitez modifier, créez un nouveau frontend ou éditez-en un existant. + +Dans l'onglet `Frontends`{.action}, cliquez sur le bouton `Ajouter un frontend`{.action} pour en créer un nouveau.
+Une fenêtre d'édition apparait alors, sélectionnez le protocole `HTTPS`. Ensuite, renseignez le champ `Ferme par défaut`.
+Enfin, ouvrez les paramètres avancés et renseignez le champ `Redirection HTTP`. + +![Configuration la terminaison SSL d'un Frontend](images/enable_ssl_terminaison.png){.thumbnail} + +Une fois le frontend créé, une bannière apparaîtra vous invitant à `Appliquer la configuration`{.action} pour déployer vos changements dans la zone concernée. + +#### Commander le certificate SSL gratuit + +Dans l'onglet `Certificats SSL`{.action}, cliquez sur le bouton `Commander un certificat SSL`{.action} pour en créer un nouveau. Une fenêtre d'édition apparait alors avec un champ `FQDN` à renseigner. + +![Ajouter un certificate SSL gratuit](images/add_freecertificate.png){.thumbnail} + +#### Suivi de la commande + +Vous pourrez suivre votre commande dans l'onglet `Tâches`{.action}. La tâche correspondant à la commande d'un certificat SSL gratuit est nommée `orderFreeCertificate`. + +### Depuis l'API OVHcloud + +#### Configurer le frontend pour la terminaison SSL + +Dans l'API, la terminaison SSL est spécifiée par le booléen `ssl`. Pour activer la terminaison SSL, réglez ce paramètre sur `true`, puis définissez `defaultFarmId` ou `redirectLocation` avec les valeurs correspondantes. > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/http/frontend > -Puis appliquer les modifications : +Appliquez ensuite les modifications : > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh > -## Commander le certificate SSL gratuit +#### Commander le certificat SSL gratuit -### Via le Manager -Dans la section `Certificats SSL` de votre Manager, cliquez sur le bouton `Commander un certificat SSL`{.action} pour en créer un nouveau. Une fenêtre d'édition apparait alors avec un champ `FQDN` à renseigner. - -![Ajouter un certificate SSL gratuit](images/iplb-order-ssl.png){.thumbnail} - -### Via l'API -Dans l'API, la commande se fait comme suit. Pour que la commande se finalise, il faut obligatoirement que le nom de domaine choisi pointe vers votre service OVH Load Balancer. +Dans l'API, la commande se fait via l'appel suivant : > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/freeCertificate > -## Suivi de la commande +Pour que la commande soit finalisée, il faut obligatoirement que le nom de domaine choisi pointe vers votre service OVHcloud Load Balancer. -### Via le Manager -Dans la section `Tâches`{.action} de votre Manager, les tâches relatives à la commandes d'un certificat SSL gratuit correspondent au type `orderFreeCertificate`. +#### Suivi de la commande -### Via l'API +- Retourner la liste des tâches -#### Retourner la liste des taches -Vous pouvez spécifier le type d'action orderFreeCertificate pour affiner la recherche. +Vous pouvez spécifier le type d'action `orderFreeCertificate` pour affiner la recherche. > [!api] > > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/task > -#### Retourner le statut d'une tache en particulier +- Retourner le statut d'une tâche en particulier > [!api] > > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/task/{id} > -## Livraison du certificat SSL gratuit -Une fois la commande finie, le certificat SSL est automatiquement installé sur votre service OVH Load Balancer. +Une fois la commande finie, le certificat SSL est automatiquement installé sur votre service OVHcloud Load Balancer. + +## Aller plus loin + +Échangez avec notre [communauté d'utilisateurs](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/order_freecertificate/guide.fr-fr.md b/pages/network/load_balancer/order_freecertificate/guide.fr-fr.md index 5d253388702..9f4c85e5c03 100644 --- a/pages/network/load_balancer/order_freecertificate/guide.fr-fr.md +++ b/pages/network/load_balancer/order_freecertificate/guide.fr-fr.md @@ -1,7 +1,7 @@ --- title: "Commande d'un certificat SSL gratuit" excerpt: Commander un certificat SSL gratuit pour vos services web derrière un Load Balancer -updated: 2025-10-22 +updated: 2025-10-23 --- ## Objectif @@ -98,4 +98,4 @@ Une fois la commande finie, le certificat SSL est automatiquement installé sur ## Aller plus loin -Échangez avec notre [communauté d'utilisateurs](/links/community). +Échangez avec notre [communauté d'utilisateurs](/links/community). \ No newline at end of file From f930b4add3ccdd5f6573bc72f0f765ecdc0eb08c Mon Sep 17 00:00:00 2001 From: jessica Date: Thu, 23 Oct 2025 18:06:32 -0400 Subject: [PATCH 19/23] updates and duplos --- .../case_blue_green/guide.en-asia.md | 129 ++++----- .../case_blue_green/guide.en-au.md | 129 ++++----- .../case_blue_green/guide.en-ca.md | 129 ++++----- .../case_blue_green/guide.en-gb.md | 16 +- .../case_blue_green/guide.en-sg.md | 129 ++++----- .../case_blue_green/guide.en-us.md | 129 ++++----- .../case_blue_green/guide.fr-ca.md | 249 ++++++++++-------- .../case_blue_green/guide.fr-fr.md | 8 +- .../create_balancing/guide.en-asia.md | 65 ++--- .../create_balancing/guide.en-au.md | 65 ++--- .../create_balancing/guide.en-ca.md | 65 ++--- .../create_balancing/guide.en-gb.md | 18 +- .../create_balancing/guide.en-sg.md | 65 ++--- .../create_balancing/guide.fr-ca.md | 75 +++--- .../create_balancing/guide.fr-fr.md | 12 +- 15 files changed, 661 insertions(+), 622 deletions(-) diff --git a/pages/network/load_balancer/case_blue_green/guide.en-asia.md b/pages/network/load_balancer/case_blue_green/guide.en-asia.md index de705cecacc..903379d1e2f 100644 --- a/pages/network/load_balancer/case_blue_green/guide.en-asia.md +++ b/pages/network/load_balancer/case_blue_green/guide.en-asia.md @@ -1,64 +1,62 @@ --- title: 'Deploying a blue-green infrastructure' excerpt: 'This guide will show you how to deploy a blue-green infrastructure with the OVHcloud Load Balancer' -updated: 2019-02-25 +updated: 2025-10-23 --- ## Objective -With this guide, we will explore a specific use for the OVHcloud Load Balancer service — configuring a service to manage production/development infrastructures easily. This is also called a blue-green infrastructure. +This guide demonstrates a specific use case for the OVHcloud Load Balancer: the configuration of a service to facilitate seamless traffic switching between production and new production candidate environments, also called a **blue-green infrastructure**. -With a `blue-green`{.action} infrastructure, you can stop your infrastructure from experiencing any downtime. The main benefit of this deployment type is that you can prepare updates and/or maintenance in an environment that is isolated from your production environment. This way, you can test your changes before they are put into production, undo them quickly if you detect any faults, and do all of this with virtually zero downtime. +With a blue-green infrastructure, you can stop your infrastructure from experiencing any downtime. The main benefit of this deployment type is that you can prepare updates and/or maintenance in an environment that is isolated from your production environment. This way, you can test your changes before they are put into production, undo them quickly if you detect any faults, and do all of this with virtually zero downtime. **This guide will show you how to deploy a blue-green infrastructure with the OVHcloud Load Balancer.** ## Requirements -To deploy a `blue-green`{.action} infrastructure, you need the following components: +To deploy a blue-green infrastructure, you need the following components: -- an OVHcloud Load Balancer service -- a first server that hosts your production infrastructure -- a second server with a similar infrastructure, dedicated to development +- An [OVHcloud Load Balancer](/links/network/load-balancer) service +- Access to the [OVHcloud Control Panel](/links/manager) +- Two [dedicated servers](/links/bare-metal/bare-metal), one hosting your production environment, and a similarly configured server hosting your staging environment ## Instructions ### Scenario -The scenario we’ll describe here is as follows... +You have an infrastructure designed to host your live website. -You have an infrastructure that you can use to put your website online. +This environment hosts the website’s code, in addition to all essential applications (web servers, database servers, etc.). You need to update your applications and/or your code on a regular basis. You want to be able to test your updates without impacting the website's availability or functionality for end-users. -This infrastructure hosts your website’s code, and it also hosts the applications (web servers, database servers, etc.) required to put your website online. You need to update your applications and/or your code on a regular basis. You want to be able to test your updates without the risk of affecting your website’s availability to customers, or stopping the website from working properly. +One way to achieve this is by deploying a blue-green infrastructure. -One way to achieve this is by deploying a `blue-green`{.action} infrastructure. +The principle of a blue-green deployment involves being able to switch easily from a development infrastructure to a production infrastructure, and vice versa. This switch must be done in a way that is transparent for your users. To do this, public traffic will be routed to the standard HTTP port 80 for access to the production infrastructure, and a non-standard port, such as 8888, will be used to access the development infrastructure. -The principle of a `blue-green`{.action} deployment involves being able to switch easily from a development infrastructure to a production infrastructure, and vice versa. This switch must be done in a way that is transparent for your users. To do this, we will assign the standard HTTP port 80 for access to the production infrastructure, and the arbitrary port 8888 to access the development infrastructure. +## Deploy the infrastructures -## Deploy the infrastructures. - -In the scenario we are using, your IP Load Balancer service plays a central role. It is the element you use to expose your two infrastructures (production and development) to different users at the same time. +In this scenario, your Load Balancer service plays a central role. It is the element you use to expose your two infrastructures (production and development) to different users at the same time. The production infrastructure can be accessed by your customers on the standard HTTP service (port 80), and your development infrastructure can be accessed by developers and admins on the non-standard port 8888. -During the initial setup phase, we will arbitrarily assign a role to each of the parts of our infrastructure. `Infrastructure A`{.action} will be assigned to production, while `infrastructure B`{.action} will be assigned to development. At this stage, we will consider them to be similar to one another. +During the initial setup phase, roles are provisionally assigned to each infrastructure component. **Infrastructure A** serves as the initial production environment, while **Infrastructure B** serves as the staging environment. At this stage, we will consider them to be similar to one another. -A `blue-green`{.action} infrastructure involves switching from infrastructure A to infrastructure B, when infrastructure B is ready to expose your website after your changes have been applied and tested. The IP Load Balancer will manage this switch. +A blue-green infrastructure involves switching from infrastructure A to infrastructure B, once infrastructure B has been fully updated and validated. The Load Balancer will manage this switch. The diagram below gives a general idea of the architecture: ![General diagram of blue-green architecture](images/scheme.png){.thumbnail} -### Infrastructure A. +### Infrastructure A -This infrastructure is made up of a server farm that will later be associated with a front-end of your IP Load Balancer. This farm will expose an HTTP, TCP or UDP service to the front-end. It also balances loads by sending the front-end’s incoming traffic to the servers. For more detail on the role of various component of the OVHcloud Load Balancer service, you can read the following guide: [Introduction to the OVHcloud Load Balancer](/pages/network/load_balancer/use_presentation){.ref}. +This infrastructure is made up of a server farm that will later be associated with a front-end of your Load Balancer. This farm will expose an HTTP, TCP or UDP service to the front-end. It also balances loads by sending the front-end’s incoming traffic to the servers. For more details on the role of the various components of the OVHcloud Load Balancer service, please refer to the following guide: [Introduction to the OVHcloud Load Balancer](/pages/network/load_balancer/use_presentation). In our scenario, we will declare a farm of servers for the HTTP service. Please note that you can create as many farms (as well as TCP and/or UDP services) as are required for your final service to be exposed to your customers. -#### Via the OVHcloud Control Panel: +#### Via the OVHcloud Control Panel ![Add a new HTTP farm dedicated to infrastructure A](images/ferme1.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -69,7 +67,7 @@ In our scenario, we will declare a farm of servers for the HTTP service. Please |---|---| |serviceName|Your Load Balancer service ID| -With the additional calls listed below, you can list, modify and delete your server farms respectively. +With the additional calls listed below, you can list, modify and delete your server farms respectively: > [!api] > @@ -86,15 +84,15 @@ With the additional calls listed below, you can list, modify and delete your ser > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/http/farm > -Associate a server with your farm, if it is a physical server hosting your production infrastructure. The service exposed to the front-end is supplied by the server’s port 8080. Please note that you can associate one or more servers with each farm (to balance the load and/or offer higher fault tolerance, for ex.). +Link a dedicated server to your farm if it hosts your production infrastructure. The service is exposed to the front-end via the server’s port 8080. Note that you may LINK one or more servers with each farm (for example, to balance the load or offer higher fault tolerance). -#### Via the OVHcloud Control Panel: +#### Via the OVHcloud Control Panel ![Add a new server to the farm HTTP A](images/serveur1.png){.thumbnail} ![Enter the HTTP A server’s configuration](images/server1.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -109,7 +107,7 @@ Associate a server with your farm, if it is a physical server hosting your produ |displayName||The name of the server associated with your farm|HTTP A server| |port||The server port associated with your farm|8080| -With the additional calls listed below, you can list, modify and delete your servers respectively. +With the additional calls listed below, you can list, modify and delete your servers respectively: > [!api] > @@ -126,19 +124,19 @@ With the additional calls listed below, you can list, modify and delete your ser > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/http/farm/{farmId}/server > -### Infrastructure B. +### Infrastructure B -Functionally, this second infrastructure is identical to the first. It is also composed of a server farm that will later be associated with a second front-end of your IP Load Balancer. This server farm exposes the same service to the front-end as the first server farm. This service is supplied on the servers by port 8080. +Functionally, this second infrastructure is identical to the first. It is also composed of a server farm that will later be associated with a second front-end of your Load Balancer. This server farm exposes the same service to the front-end as the first server farm. This service is supplied on the servers by port 8080. Deploy the server farm for the HTTP service (and/or any other TCP or UDP services required for your final service to be exposed to your customers). -#### Via the Sunrise Control Panel: +#### Via the OVHcloud Control Panel ![Add a new HTTP farm dedicated to infrastructure B](images/ferme2.png){.thumbnail} ![Create a second farm dedicated to infrastructure B](images/backend2.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -151,13 +149,13 @@ Deploy the server farm for the HTTP service (and/or any other TCP or UDP service Associate a server with your farm. Here, it involves one or more physical servers hosting your development infrastructure. -#### Via the OVHcloud Control Panel: +#### Via the OVHcloud Control Panel ![Add a new server to the farm HTTP B](images/serveur2.png){.thumbnail} ![Enter the HTTP B server’s configuration](images/server2.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -176,9 +174,9 @@ At this stage, here is the configuration status for your two farms: ![Farm configuration](images/farms.png){.thumbnail} -## Front-ends. +## Front-ends -The magic of `blue-green`{.action} deployment lies in the configuration of your front-ends. At this stage, we have configure two functionally identical infrastructures. For both infrastructures, you have declared one or more server farms, each with their own set of associated servers. +The magic of blue-green deployment lies in the configuration of your front-ends. At this stage, we have configured two functionally identical infrastructures. For both infrastructures, you have declared one or more server farms, each with their own set of associated servers. To switch simply from one infrastructure to another, we will use front-ends. @@ -186,19 +184,20 @@ To do this, we need to declare two front-ends. The first one will give you acces > [!warning] > -> If the final service you expose to your customers requires several server farms (e.g. ports 80 and 443), you will need to declare a `front-end`{.action} for each of your farms. +> If the final service you expose to your customers requires several server farms (e.g. ports 80 and 443), you will need to declare a **front-end** for each of your farms. > -### Blue front-end. -This `front-end`{.action} is dedicated to accessing the production infrastructure. The ports exposed to your customers are the standard ports for accessing the service. In this case, we are exposing a HTTP service, so we will use port 80 (443 if you would like an SSL termination). +### Blue front-end + +This **front-end** is dedicated to accessing the production infrastructure. The ports exposed to your customers are the standard ports for accessing the service. In this case, we are exposing an HTTP service, so we will use port 80 (443 if you would like an SSL termination). -#### Via the OVHcloud Control Panel: +#### Via the OVHcloud Control Panel ![Adding a front-end dedicated to production, a blue front-end](images/frontend1.png){.thumbnail} ![Enter the blue front-end’s configuration](images/fblue.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -213,17 +212,17 @@ This `front-end`{.action} is dedicated to accessing the production infrastructur |port|Required|The port exposed to your customers by your front-end|80| |zone|Required|The zone in which you want to deploy your front-end|all| -### Green front-end. +### Green front-end -This `front-end`{.action} is dedicated to accessing the development infrastructure. The ports exposed to your customers will be non-standard ports that you can choose arbitrarily. In this case, we will expose the HTTP development service on port 8888. +This **front-end** is dedicated to accessing the development infrastructure. The ports exposed to your customers will be non-standard ports that you can choose arbitrarily. In this case, we will expose the HTTP development service on port 8888. -#### Via the OVHcloud Control Panel: +#### Via the OVHcloud Control Panel ![Add the green front-end, dedicated to development](images/frontend2.png){.thumbnail} ![Enter the green front-end’s configuration](images/fgreen.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -238,17 +237,17 @@ This `front-end`{.action} is dedicated to accessing the development infrastructu |port|Required|The port exposed to your customers by your front-end|8888| |zone|Required|The zone in which you want to deploy your front-end|all| -## Manage the deployments. +## Manage the deployments -### Initial deployment. +### Initial deployment -Once you have finished configuring the components of the OVHcloud Load Balancer service, you now just need to apply your changes. +Once you have finished configuring the components of the OVHcloud Load Balancer service, the only thing left to do is apply your changes. -#### Via the OVHcloud Control Panel: +#### Via the OVHcloud Control Panel ![Apply your changes to the zone](images/deploy.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -259,30 +258,30 @@ Once you have finished configuring the components of the OVHcloud Load Balancer |---|---| |serviceName|Your Load Balancer service ID| -### The production/pre-production switch. +### The production/staging switch -At this stage, our initial environment is deployed and ready to use. How do we use it? - -To put it simply, you just need to switch over your front-ends from one server farm to another. +At this stage, our initial environment is deployed and ready to use. Now, you need to switch over your front-ends from one server farm to another. Let’s take a look at our scenario: -- The production infrastructure (A) is deployed on `HTTP farm A`{.action} (id 77212), which in turn is attached to `HTTP server A`{.action}. This infrastructure can be accessed through the `blue front-end`{.action}. -- The development infrastructure (B) is deployed on `HTTP farm B`{.action} (id 77213), which in turn is attached to `HTTP server B`{.action}. This infrastructure can be accessed through the `green front-end`{.action}. +- The production infrastructure (A) is deployed on **HTTP farm A** (id 77212), which in turn is attached to **HTTP server A**. This infrastructure can be accessed through the **blue front-end**. +- The development infrastructure (B) is deployed on **HTTP farm B** (id 77213), which in turn is attached to **HTTP server B**. This infrastructure can be accessed through the **green front-end**. -Once you have modified/applied updates to `infrastructure B`{.action} and checked that the service is working properly, you decide to put it into production. +Once you have modified/applied updates to **infrastructure B** and checked that the service is working properly, you can decide to put it into production. To switch between the two farms, you can simply update your different front-ends by modifying the ID of the farm it is attached to, and applying the modification. -The `blue front-end`{.action} (id 70089) will then be associated with `Farm B`{.action} (infrastructure B, new production, id 77213). +The **blue front-end** (id 70089) will then be associated with **Farm B** (infrastructure B, new production, id 77213). -The `green front-end`{.action} (id 70090) will then be associated with `Farm A`{.action} (infrastructure A, new development, id 77212). +The **green front-end** (id 70090) will then be associated with **Farm A** (infrastructure A, new development, id 77212). -This should be the result on the Sunrise Control Panel after updating the front-ends and applying the new configuration: +This should be the result on the OVHcloud Control Panel after updating the front-ends and applying the new configuration: ![Result after updating front-ends](images/switch.png){.thumbnail} -#### Via the API: updating front-ends and applying modifications#### +#### Via the OVHcloud API + +- Updating front-ends and applying modifications: > [!api] > @@ -306,7 +305,7 @@ This should be the result on the Sunrise Control Panel after updating the front- |frontendId|Your production front-end ID|70090| |defaultFarmId|Your development server farm ID|77212| -#### To apply your changes and effectively switch over the production and development environments: +- To apply your changes and effectively switch over the production and development environments: > [!api] > @@ -317,12 +316,16 @@ This should be the result on the Sunrise Control Panel after updating the front- |---|---| |serviceName|Your Load Balancer service ID| -## Go further +## Conclusion -You now have an infrastructure you can use to simply and efficiently manage `blue-green deployments`{.action}. +You have successfully implemented a highly available infrastructure for managing blue-green deployments. -Developers have access to a development environment on port 8888 (or whichever other port you would prefer to define), while your customers continue to access the service in production via the standard HTTP port (80 in our case, for example). +Developers have access to a development environment on port 8888 (or any configurable non-standard port), while your customers continue to access the service in production via the standard HTTP port (80). The infrastructure presented here is limited to just one port, but it can be expanded by adding other ports. For example, you can also expose your website on the standard HTTPS port (443). You can do this by defining new farms dedicated to each port you want to expose, and associating them with their corresponding front-ends (one for the standard port exposed in production, the second for the arbitrary port dedicated to development). Another way to consolidate your infrastructure even further is by multiplying the servers attached to your farms. This way, you can make your services more redundant (guaranteeing availability as a result), and also add a load balancing capacity. + +## Go further + +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/case_blue_green/guide.en-au.md b/pages/network/load_balancer/case_blue_green/guide.en-au.md index de705cecacc..903379d1e2f 100644 --- a/pages/network/load_balancer/case_blue_green/guide.en-au.md +++ b/pages/network/load_balancer/case_blue_green/guide.en-au.md @@ -1,64 +1,62 @@ --- title: 'Deploying a blue-green infrastructure' excerpt: 'This guide will show you how to deploy a blue-green infrastructure with the OVHcloud Load Balancer' -updated: 2019-02-25 +updated: 2025-10-23 --- ## Objective -With this guide, we will explore a specific use for the OVHcloud Load Balancer service — configuring a service to manage production/development infrastructures easily. This is also called a blue-green infrastructure. +This guide demonstrates a specific use case for the OVHcloud Load Balancer: the configuration of a service to facilitate seamless traffic switching between production and new production candidate environments, also called a **blue-green infrastructure**. -With a `blue-green`{.action} infrastructure, you can stop your infrastructure from experiencing any downtime. The main benefit of this deployment type is that you can prepare updates and/or maintenance in an environment that is isolated from your production environment. This way, you can test your changes before they are put into production, undo them quickly if you detect any faults, and do all of this with virtually zero downtime. +With a blue-green infrastructure, you can stop your infrastructure from experiencing any downtime. The main benefit of this deployment type is that you can prepare updates and/or maintenance in an environment that is isolated from your production environment. This way, you can test your changes before they are put into production, undo them quickly if you detect any faults, and do all of this with virtually zero downtime. **This guide will show you how to deploy a blue-green infrastructure with the OVHcloud Load Balancer.** ## Requirements -To deploy a `blue-green`{.action} infrastructure, you need the following components: +To deploy a blue-green infrastructure, you need the following components: -- an OVHcloud Load Balancer service -- a first server that hosts your production infrastructure -- a second server with a similar infrastructure, dedicated to development +- An [OVHcloud Load Balancer](/links/network/load-balancer) service +- Access to the [OVHcloud Control Panel](/links/manager) +- Two [dedicated servers](/links/bare-metal/bare-metal), one hosting your production environment, and a similarly configured server hosting your staging environment ## Instructions ### Scenario -The scenario we’ll describe here is as follows... +You have an infrastructure designed to host your live website. -You have an infrastructure that you can use to put your website online. +This environment hosts the website’s code, in addition to all essential applications (web servers, database servers, etc.). You need to update your applications and/or your code on a regular basis. You want to be able to test your updates without impacting the website's availability or functionality for end-users. -This infrastructure hosts your website’s code, and it also hosts the applications (web servers, database servers, etc.) required to put your website online. You need to update your applications and/or your code on a regular basis. You want to be able to test your updates without the risk of affecting your website’s availability to customers, or stopping the website from working properly. +One way to achieve this is by deploying a blue-green infrastructure. -One way to achieve this is by deploying a `blue-green`{.action} infrastructure. +The principle of a blue-green deployment involves being able to switch easily from a development infrastructure to a production infrastructure, and vice versa. This switch must be done in a way that is transparent for your users. To do this, public traffic will be routed to the standard HTTP port 80 for access to the production infrastructure, and a non-standard port, such as 8888, will be used to access the development infrastructure. -The principle of a `blue-green`{.action} deployment involves being able to switch easily from a development infrastructure to a production infrastructure, and vice versa. This switch must be done in a way that is transparent for your users. To do this, we will assign the standard HTTP port 80 for access to the production infrastructure, and the arbitrary port 8888 to access the development infrastructure. +## Deploy the infrastructures -## Deploy the infrastructures. - -In the scenario we are using, your IP Load Balancer service plays a central role. It is the element you use to expose your two infrastructures (production and development) to different users at the same time. +In this scenario, your Load Balancer service plays a central role. It is the element you use to expose your two infrastructures (production and development) to different users at the same time. The production infrastructure can be accessed by your customers on the standard HTTP service (port 80), and your development infrastructure can be accessed by developers and admins on the non-standard port 8888. -During the initial setup phase, we will arbitrarily assign a role to each of the parts of our infrastructure. `Infrastructure A`{.action} will be assigned to production, while `infrastructure B`{.action} will be assigned to development. At this stage, we will consider them to be similar to one another. +During the initial setup phase, roles are provisionally assigned to each infrastructure component. **Infrastructure A** serves as the initial production environment, while **Infrastructure B** serves as the staging environment. At this stage, we will consider them to be similar to one another. -A `blue-green`{.action} infrastructure involves switching from infrastructure A to infrastructure B, when infrastructure B is ready to expose your website after your changes have been applied and tested. The IP Load Balancer will manage this switch. +A blue-green infrastructure involves switching from infrastructure A to infrastructure B, once infrastructure B has been fully updated and validated. The Load Balancer will manage this switch. The diagram below gives a general idea of the architecture: ![General diagram of blue-green architecture](images/scheme.png){.thumbnail} -### Infrastructure A. +### Infrastructure A -This infrastructure is made up of a server farm that will later be associated with a front-end of your IP Load Balancer. This farm will expose an HTTP, TCP or UDP service to the front-end. It also balances loads by sending the front-end’s incoming traffic to the servers. For more detail on the role of various component of the OVHcloud Load Balancer service, you can read the following guide: [Introduction to the OVHcloud Load Balancer](/pages/network/load_balancer/use_presentation){.ref}. +This infrastructure is made up of a server farm that will later be associated with a front-end of your Load Balancer. This farm will expose an HTTP, TCP or UDP service to the front-end. It also balances loads by sending the front-end’s incoming traffic to the servers. For more details on the role of the various components of the OVHcloud Load Balancer service, please refer to the following guide: [Introduction to the OVHcloud Load Balancer](/pages/network/load_balancer/use_presentation). In our scenario, we will declare a farm of servers for the HTTP service. Please note that you can create as many farms (as well as TCP and/or UDP services) as are required for your final service to be exposed to your customers. -#### Via the OVHcloud Control Panel: +#### Via the OVHcloud Control Panel ![Add a new HTTP farm dedicated to infrastructure A](images/ferme1.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -69,7 +67,7 @@ In our scenario, we will declare a farm of servers for the HTTP service. Please |---|---| |serviceName|Your Load Balancer service ID| -With the additional calls listed below, you can list, modify and delete your server farms respectively. +With the additional calls listed below, you can list, modify and delete your server farms respectively: > [!api] > @@ -86,15 +84,15 @@ With the additional calls listed below, you can list, modify and delete your ser > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/http/farm > -Associate a server with your farm, if it is a physical server hosting your production infrastructure. The service exposed to the front-end is supplied by the server’s port 8080. Please note that you can associate one or more servers with each farm (to balance the load and/or offer higher fault tolerance, for ex.). +Link a dedicated server to your farm if it hosts your production infrastructure. The service is exposed to the front-end via the server’s port 8080. Note that you may LINK one or more servers with each farm (for example, to balance the load or offer higher fault tolerance). -#### Via the OVHcloud Control Panel: +#### Via the OVHcloud Control Panel ![Add a new server to the farm HTTP A](images/serveur1.png){.thumbnail} ![Enter the HTTP A server’s configuration](images/server1.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -109,7 +107,7 @@ Associate a server with your farm, if it is a physical server hosting your produ |displayName||The name of the server associated with your farm|HTTP A server| |port||The server port associated with your farm|8080| -With the additional calls listed below, you can list, modify and delete your servers respectively. +With the additional calls listed below, you can list, modify and delete your servers respectively: > [!api] > @@ -126,19 +124,19 @@ With the additional calls listed below, you can list, modify and delete your ser > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/http/farm/{farmId}/server > -### Infrastructure B. +### Infrastructure B -Functionally, this second infrastructure is identical to the first. It is also composed of a server farm that will later be associated with a second front-end of your IP Load Balancer. This server farm exposes the same service to the front-end as the first server farm. This service is supplied on the servers by port 8080. +Functionally, this second infrastructure is identical to the first. It is also composed of a server farm that will later be associated with a second front-end of your Load Balancer. This server farm exposes the same service to the front-end as the first server farm. This service is supplied on the servers by port 8080. Deploy the server farm for the HTTP service (and/or any other TCP or UDP services required for your final service to be exposed to your customers). -#### Via the Sunrise Control Panel: +#### Via the OVHcloud Control Panel ![Add a new HTTP farm dedicated to infrastructure B](images/ferme2.png){.thumbnail} ![Create a second farm dedicated to infrastructure B](images/backend2.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -151,13 +149,13 @@ Deploy the server farm for the HTTP service (and/or any other TCP or UDP service Associate a server with your farm. Here, it involves one or more physical servers hosting your development infrastructure. -#### Via the OVHcloud Control Panel: +#### Via the OVHcloud Control Panel ![Add a new server to the farm HTTP B](images/serveur2.png){.thumbnail} ![Enter the HTTP B server’s configuration](images/server2.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -176,9 +174,9 @@ At this stage, here is the configuration status for your two farms: ![Farm configuration](images/farms.png){.thumbnail} -## Front-ends. +## Front-ends -The magic of `blue-green`{.action} deployment lies in the configuration of your front-ends. At this stage, we have configure two functionally identical infrastructures. For both infrastructures, you have declared one or more server farms, each with their own set of associated servers. +The magic of blue-green deployment lies in the configuration of your front-ends. At this stage, we have configured two functionally identical infrastructures. For both infrastructures, you have declared one or more server farms, each with their own set of associated servers. To switch simply from one infrastructure to another, we will use front-ends. @@ -186,19 +184,20 @@ To do this, we need to declare two front-ends. The first one will give you acces > [!warning] > -> If the final service you expose to your customers requires several server farms (e.g. ports 80 and 443), you will need to declare a `front-end`{.action} for each of your farms. +> If the final service you expose to your customers requires several server farms (e.g. ports 80 and 443), you will need to declare a **front-end** for each of your farms. > -### Blue front-end. -This `front-end`{.action} is dedicated to accessing the production infrastructure. The ports exposed to your customers are the standard ports for accessing the service. In this case, we are exposing a HTTP service, so we will use port 80 (443 if you would like an SSL termination). +### Blue front-end + +This **front-end** is dedicated to accessing the production infrastructure. The ports exposed to your customers are the standard ports for accessing the service. In this case, we are exposing an HTTP service, so we will use port 80 (443 if you would like an SSL termination). -#### Via the OVHcloud Control Panel: +#### Via the OVHcloud Control Panel ![Adding a front-end dedicated to production, a blue front-end](images/frontend1.png){.thumbnail} ![Enter the blue front-end’s configuration](images/fblue.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -213,17 +212,17 @@ This `front-end`{.action} is dedicated to accessing the production infrastructur |port|Required|The port exposed to your customers by your front-end|80| |zone|Required|The zone in which you want to deploy your front-end|all| -### Green front-end. +### Green front-end -This `front-end`{.action} is dedicated to accessing the development infrastructure. The ports exposed to your customers will be non-standard ports that you can choose arbitrarily. In this case, we will expose the HTTP development service on port 8888. +This **front-end** is dedicated to accessing the development infrastructure. The ports exposed to your customers will be non-standard ports that you can choose arbitrarily. In this case, we will expose the HTTP development service on port 8888. -#### Via the OVHcloud Control Panel: +#### Via the OVHcloud Control Panel ![Add the green front-end, dedicated to development](images/frontend2.png){.thumbnail} ![Enter the green front-end’s configuration](images/fgreen.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -238,17 +237,17 @@ This `front-end`{.action} is dedicated to accessing the development infrastructu |port|Required|The port exposed to your customers by your front-end|8888| |zone|Required|The zone in which you want to deploy your front-end|all| -## Manage the deployments. +## Manage the deployments -### Initial deployment. +### Initial deployment -Once you have finished configuring the components of the OVHcloud Load Balancer service, you now just need to apply your changes. +Once you have finished configuring the components of the OVHcloud Load Balancer service, the only thing left to do is apply your changes. -#### Via the OVHcloud Control Panel: +#### Via the OVHcloud Control Panel ![Apply your changes to the zone](images/deploy.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -259,30 +258,30 @@ Once you have finished configuring the components of the OVHcloud Load Balancer |---|---| |serviceName|Your Load Balancer service ID| -### The production/pre-production switch. +### The production/staging switch -At this stage, our initial environment is deployed and ready to use. How do we use it? - -To put it simply, you just need to switch over your front-ends from one server farm to another. +At this stage, our initial environment is deployed and ready to use. Now, you need to switch over your front-ends from one server farm to another. Let’s take a look at our scenario: -- The production infrastructure (A) is deployed on `HTTP farm A`{.action} (id 77212), which in turn is attached to `HTTP server A`{.action}. This infrastructure can be accessed through the `blue front-end`{.action}. -- The development infrastructure (B) is deployed on `HTTP farm B`{.action} (id 77213), which in turn is attached to `HTTP server B`{.action}. This infrastructure can be accessed through the `green front-end`{.action}. +- The production infrastructure (A) is deployed on **HTTP farm A** (id 77212), which in turn is attached to **HTTP server A**. This infrastructure can be accessed through the **blue front-end**. +- The development infrastructure (B) is deployed on **HTTP farm B** (id 77213), which in turn is attached to **HTTP server B**. This infrastructure can be accessed through the **green front-end**. -Once you have modified/applied updates to `infrastructure B`{.action} and checked that the service is working properly, you decide to put it into production. +Once you have modified/applied updates to **infrastructure B** and checked that the service is working properly, you can decide to put it into production. To switch between the two farms, you can simply update your different front-ends by modifying the ID of the farm it is attached to, and applying the modification. -The `blue front-end`{.action} (id 70089) will then be associated with `Farm B`{.action} (infrastructure B, new production, id 77213). +The **blue front-end** (id 70089) will then be associated with **Farm B** (infrastructure B, new production, id 77213). -The `green front-end`{.action} (id 70090) will then be associated with `Farm A`{.action} (infrastructure A, new development, id 77212). +The **green front-end** (id 70090) will then be associated with **Farm A** (infrastructure A, new development, id 77212). -This should be the result on the Sunrise Control Panel after updating the front-ends and applying the new configuration: +This should be the result on the OVHcloud Control Panel after updating the front-ends and applying the new configuration: ![Result after updating front-ends](images/switch.png){.thumbnail} -#### Via the API: updating front-ends and applying modifications#### +#### Via the OVHcloud API + +- Updating front-ends and applying modifications: > [!api] > @@ -306,7 +305,7 @@ This should be the result on the Sunrise Control Panel after updating the front- |frontendId|Your production front-end ID|70090| |defaultFarmId|Your development server farm ID|77212| -#### To apply your changes and effectively switch over the production and development environments: +- To apply your changes and effectively switch over the production and development environments: > [!api] > @@ -317,12 +316,16 @@ This should be the result on the Sunrise Control Panel after updating the front- |---|---| |serviceName|Your Load Balancer service ID| -## Go further +## Conclusion -You now have an infrastructure you can use to simply and efficiently manage `blue-green deployments`{.action}. +You have successfully implemented a highly available infrastructure for managing blue-green deployments. -Developers have access to a development environment on port 8888 (or whichever other port you would prefer to define), while your customers continue to access the service in production via the standard HTTP port (80 in our case, for example). +Developers have access to a development environment on port 8888 (or any configurable non-standard port), while your customers continue to access the service in production via the standard HTTP port (80). The infrastructure presented here is limited to just one port, but it can be expanded by adding other ports. For example, you can also expose your website on the standard HTTPS port (443). You can do this by defining new farms dedicated to each port you want to expose, and associating them with their corresponding front-ends (one for the standard port exposed in production, the second for the arbitrary port dedicated to development). Another way to consolidate your infrastructure even further is by multiplying the servers attached to your farms. This way, you can make your services more redundant (guaranteeing availability as a result), and also add a load balancing capacity. + +## Go further + +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/case_blue_green/guide.en-ca.md b/pages/network/load_balancer/case_blue_green/guide.en-ca.md index de705cecacc..903379d1e2f 100644 --- a/pages/network/load_balancer/case_blue_green/guide.en-ca.md +++ b/pages/network/load_balancer/case_blue_green/guide.en-ca.md @@ -1,64 +1,62 @@ --- title: 'Deploying a blue-green infrastructure' excerpt: 'This guide will show you how to deploy a blue-green infrastructure with the OVHcloud Load Balancer' -updated: 2019-02-25 +updated: 2025-10-23 --- ## Objective -With this guide, we will explore a specific use for the OVHcloud Load Balancer service — configuring a service to manage production/development infrastructures easily. This is also called a blue-green infrastructure. +This guide demonstrates a specific use case for the OVHcloud Load Balancer: the configuration of a service to facilitate seamless traffic switching between production and new production candidate environments, also called a **blue-green infrastructure**. -With a `blue-green`{.action} infrastructure, you can stop your infrastructure from experiencing any downtime. The main benefit of this deployment type is that you can prepare updates and/or maintenance in an environment that is isolated from your production environment. This way, you can test your changes before they are put into production, undo them quickly if you detect any faults, and do all of this with virtually zero downtime. +With a blue-green infrastructure, you can stop your infrastructure from experiencing any downtime. The main benefit of this deployment type is that you can prepare updates and/or maintenance in an environment that is isolated from your production environment. This way, you can test your changes before they are put into production, undo them quickly if you detect any faults, and do all of this with virtually zero downtime. **This guide will show you how to deploy a blue-green infrastructure with the OVHcloud Load Balancer.** ## Requirements -To deploy a `blue-green`{.action} infrastructure, you need the following components: +To deploy a blue-green infrastructure, you need the following components: -- an OVHcloud Load Balancer service -- a first server that hosts your production infrastructure -- a second server with a similar infrastructure, dedicated to development +- An [OVHcloud Load Balancer](/links/network/load-balancer) service +- Access to the [OVHcloud Control Panel](/links/manager) +- Two [dedicated servers](/links/bare-metal/bare-metal), one hosting your production environment, and a similarly configured server hosting your staging environment ## Instructions ### Scenario -The scenario we’ll describe here is as follows... +You have an infrastructure designed to host your live website. -You have an infrastructure that you can use to put your website online. +This environment hosts the website’s code, in addition to all essential applications (web servers, database servers, etc.). You need to update your applications and/or your code on a regular basis. You want to be able to test your updates without impacting the website's availability or functionality for end-users. -This infrastructure hosts your website’s code, and it also hosts the applications (web servers, database servers, etc.) required to put your website online. You need to update your applications and/or your code on a regular basis. You want to be able to test your updates without the risk of affecting your website’s availability to customers, or stopping the website from working properly. +One way to achieve this is by deploying a blue-green infrastructure. -One way to achieve this is by deploying a `blue-green`{.action} infrastructure. +The principle of a blue-green deployment involves being able to switch easily from a development infrastructure to a production infrastructure, and vice versa. This switch must be done in a way that is transparent for your users. To do this, public traffic will be routed to the standard HTTP port 80 for access to the production infrastructure, and a non-standard port, such as 8888, will be used to access the development infrastructure. -The principle of a `blue-green`{.action} deployment involves being able to switch easily from a development infrastructure to a production infrastructure, and vice versa. This switch must be done in a way that is transparent for your users. To do this, we will assign the standard HTTP port 80 for access to the production infrastructure, and the arbitrary port 8888 to access the development infrastructure. +## Deploy the infrastructures -## Deploy the infrastructures. - -In the scenario we are using, your IP Load Balancer service plays a central role. It is the element you use to expose your two infrastructures (production and development) to different users at the same time. +In this scenario, your Load Balancer service plays a central role. It is the element you use to expose your two infrastructures (production and development) to different users at the same time. The production infrastructure can be accessed by your customers on the standard HTTP service (port 80), and your development infrastructure can be accessed by developers and admins on the non-standard port 8888. -During the initial setup phase, we will arbitrarily assign a role to each of the parts of our infrastructure. `Infrastructure A`{.action} will be assigned to production, while `infrastructure B`{.action} will be assigned to development. At this stage, we will consider them to be similar to one another. +During the initial setup phase, roles are provisionally assigned to each infrastructure component. **Infrastructure A** serves as the initial production environment, while **Infrastructure B** serves as the staging environment. At this stage, we will consider them to be similar to one another. -A `blue-green`{.action} infrastructure involves switching from infrastructure A to infrastructure B, when infrastructure B is ready to expose your website after your changes have been applied and tested. The IP Load Balancer will manage this switch. +A blue-green infrastructure involves switching from infrastructure A to infrastructure B, once infrastructure B has been fully updated and validated. The Load Balancer will manage this switch. The diagram below gives a general idea of the architecture: ![General diagram of blue-green architecture](images/scheme.png){.thumbnail} -### Infrastructure A. +### Infrastructure A -This infrastructure is made up of a server farm that will later be associated with a front-end of your IP Load Balancer. This farm will expose an HTTP, TCP or UDP service to the front-end. It also balances loads by sending the front-end’s incoming traffic to the servers. For more detail on the role of various component of the OVHcloud Load Balancer service, you can read the following guide: [Introduction to the OVHcloud Load Balancer](/pages/network/load_balancer/use_presentation){.ref}. +This infrastructure is made up of a server farm that will later be associated with a front-end of your Load Balancer. This farm will expose an HTTP, TCP or UDP service to the front-end. It also balances loads by sending the front-end’s incoming traffic to the servers. For more details on the role of the various components of the OVHcloud Load Balancer service, please refer to the following guide: [Introduction to the OVHcloud Load Balancer](/pages/network/load_balancer/use_presentation). In our scenario, we will declare a farm of servers for the HTTP service. Please note that you can create as many farms (as well as TCP and/or UDP services) as are required for your final service to be exposed to your customers. -#### Via the OVHcloud Control Panel: +#### Via the OVHcloud Control Panel ![Add a new HTTP farm dedicated to infrastructure A](images/ferme1.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -69,7 +67,7 @@ In our scenario, we will declare a farm of servers for the HTTP service. Please |---|---| |serviceName|Your Load Balancer service ID| -With the additional calls listed below, you can list, modify and delete your server farms respectively. +With the additional calls listed below, you can list, modify and delete your server farms respectively: > [!api] > @@ -86,15 +84,15 @@ With the additional calls listed below, you can list, modify and delete your ser > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/http/farm > -Associate a server with your farm, if it is a physical server hosting your production infrastructure. The service exposed to the front-end is supplied by the server’s port 8080. Please note that you can associate one or more servers with each farm (to balance the load and/or offer higher fault tolerance, for ex.). +Link a dedicated server to your farm if it hosts your production infrastructure. The service is exposed to the front-end via the server’s port 8080. Note that you may LINK one or more servers with each farm (for example, to balance the load or offer higher fault tolerance). -#### Via the OVHcloud Control Panel: +#### Via the OVHcloud Control Panel ![Add a new server to the farm HTTP A](images/serveur1.png){.thumbnail} ![Enter the HTTP A server’s configuration](images/server1.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -109,7 +107,7 @@ Associate a server with your farm, if it is a physical server hosting your produ |displayName||The name of the server associated with your farm|HTTP A server| |port||The server port associated with your farm|8080| -With the additional calls listed below, you can list, modify and delete your servers respectively. +With the additional calls listed below, you can list, modify and delete your servers respectively: > [!api] > @@ -126,19 +124,19 @@ With the additional calls listed below, you can list, modify and delete your ser > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/http/farm/{farmId}/server > -### Infrastructure B. +### Infrastructure B -Functionally, this second infrastructure is identical to the first. It is also composed of a server farm that will later be associated with a second front-end of your IP Load Balancer. This server farm exposes the same service to the front-end as the first server farm. This service is supplied on the servers by port 8080. +Functionally, this second infrastructure is identical to the first. It is also composed of a server farm that will later be associated with a second front-end of your Load Balancer. This server farm exposes the same service to the front-end as the first server farm. This service is supplied on the servers by port 8080. Deploy the server farm for the HTTP service (and/or any other TCP or UDP services required for your final service to be exposed to your customers). -#### Via the Sunrise Control Panel: +#### Via the OVHcloud Control Panel ![Add a new HTTP farm dedicated to infrastructure B](images/ferme2.png){.thumbnail} ![Create a second farm dedicated to infrastructure B](images/backend2.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -151,13 +149,13 @@ Deploy the server farm for the HTTP service (and/or any other TCP or UDP service Associate a server with your farm. Here, it involves one or more physical servers hosting your development infrastructure. -#### Via the OVHcloud Control Panel: +#### Via the OVHcloud Control Panel ![Add a new server to the farm HTTP B](images/serveur2.png){.thumbnail} ![Enter the HTTP B server’s configuration](images/server2.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -176,9 +174,9 @@ At this stage, here is the configuration status for your two farms: ![Farm configuration](images/farms.png){.thumbnail} -## Front-ends. +## Front-ends -The magic of `blue-green`{.action} deployment lies in the configuration of your front-ends. At this stage, we have configure two functionally identical infrastructures. For both infrastructures, you have declared one or more server farms, each with their own set of associated servers. +The magic of blue-green deployment lies in the configuration of your front-ends. At this stage, we have configured two functionally identical infrastructures. For both infrastructures, you have declared one or more server farms, each with their own set of associated servers. To switch simply from one infrastructure to another, we will use front-ends. @@ -186,19 +184,20 @@ To do this, we need to declare two front-ends. The first one will give you acces > [!warning] > -> If the final service you expose to your customers requires several server farms (e.g. ports 80 and 443), you will need to declare a `front-end`{.action} for each of your farms. +> If the final service you expose to your customers requires several server farms (e.g. ports 80 and 443), you will need to declare a **front-end** for each of your farms. > -### Blue front-end. -This `front-end`{.action} is dedicated to accessing the production infrastructure. The ports exposed to your customers are the standard ports for accessing the service. In this case, we are exposing a HTTP service, so we will use port 80 (443 if you would like an SSL termination). +### Blue front-end + +This **front-end** is dedicated to accessing the production infrastructure. The ports exposed to your customers are the standard ports for accessing the service. In this case, we are exposing an HTTP service, so we will use port 80 (443 if you would like an SSL termination). -#### Via the OVHcloud Control Panel: +#### Via the OVHcloud Control Panel ![Adding a front-end dedicated to production, a blue front-end](images/frontend1.png){.thumbnail} ![Enter the blue front-end’s configuration](images/fblue.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -213,17 +212,17 @@ This `front-end`{.action} is dedicated to accessing the production infrastructur |port|Required|The port exposed to your customers by your front-end|80| |zone|Required|The zone in which you want to deploy your front-end|all| -### Green front-end. +### Green front-end -This `front-end`{.action} is dedicated to accessing the development infrastructure. The ports exposed to your customers will be non-standard ports that you can choose arbitrarily. In this case, we will expose the HTTP development service on port 8888. +This **front-end** is dedicated to accessing the development infrastructure. The ports exposed to your customers will be non-standard ports that you can choose arbitrarily. In this case, we will expose the HTTP development service on port 8888. -#### Via the OVHcloud Control Panel: +#### Via the OVHcloud Control Panel ![Add the green front-end, dedicated to development](images/frontend2.png){.thumbnail} ![Enter the green front-end’s configuration](images/fgreen.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -238,17 +237,17 @@ This `front-end`{.action} is dedicated to accessing the development infrastructu |port|Required|The port exposed to your customers by your front-end|8888| |zone|Required|The zone in which you want to deploy your front-end|all| -## Manage the deployments. +## Manage the deployments -### Initial deployment. +### Initial deployment -Once you have finished configuring the components of the OVHcloud Load Balancer service, you now just need to apply your changes. +Once you have finished configuring the components of the OVHcloud Load Balancer service, the only thing left to do is apply your changes. -#### Via the OVHcloud Control Panel: +#### Via the OVHcloud Control Panel ![Apply your changes to the zone](images/deploy.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -259,30 +258,30 @@ Once you have finished configuring the components of the OVHcloud Load Balancer |---|---| |serviceName|Your Load Balancer service ID| -### The production/pre-production switch. +### The production/staging switch -At this stage, our initial environment is deployed and ready to use. How do we use it? - -To put it simply, you just need to switch over your front-ends from one server farm to another. +At this stage, our initial environment is deployed and ready to use. Now, you need to switch over your front-ends from one server farm to another. Let’s take a look at our scenario: -- The production infrastructure (A) is deployed on `HTTP farm A`{.action} (id 77212), which in turn is attached to `HTTP server A`{.action}. This infrastructure can be accessed through the `blue front-end`{.action}. -- The development infrastructure (B) is deployed on `HTTP farm B`{.action} (id 77213), which in turn is attached to `HTTP server B`{.action}. This infrastructure can be accessed through the `green front-end`{.action}. +- The production infrastructure (A) is deployed on **HTTP farm A** (id 77212), which in turn is attached to **HTTP server A**. This infrastructure can be accessed through the **blue front-end**. +- The development infrastructure (B) is deployed on **HTTP farm B** (id 77213), which in turn is attached to **HTTP server B**. This infrastructure can be accessed through the **green front-end**. -Once you have modified/applied updates to `infrastructure B`{.action} and checked that the service is working properly, you decide to put it into production. +Once you have modified/applied updates to **infrastructure B** and checked that the service is working properly, you can decide to put it into production. To switch between the two farms, you can simply update your different front-ends by modifying the ID of the farm it is attached to, and applying the modification. -The `blue front-end`{.action} (id 70089) will then be associated with `Farm B`{.action} (infrastructure B, new production, id 77213). +The **blue front-end** (id 70089) will then be associated with **Farm B** (infrastructure B, new production, id 77213). -The `green front-end`{.action} (id 70090) will then be associated with `Farm A`{.action} (infrastructure A, new development, id 77212). +The **green front-end** (id 70090) will then be associated with **Farm A** (infrastructure A, new development, id 77212). -This should be the result on the Sunrise Control Panel after updating the front-ends and applying the new configuration: +This should be the result on the OVHcloud Control Panel after updating the front-ends and applying the new configuration: ![Result after updating front-ends](images/switch.png){.thumbnail} -#### Via the API: updating front-ends and applying modifications#### +#### Via the OVHcloud API + +- Updating front-ends and applying modifications: > [!api] > @@ -306,7 +305,7 @@ This should be the result on the Sunrise Control Panel after updating the front- |frontendId|Your production front-end ID|70090| |defaultFarmId|Your development server farm ID|77212| -#### To apply your changes and effectively switch over the production and development environments: +- To apply your changes and effectively switch over the production and development environments: > [!api] > @@ -317,12 +316,16 @@ This should be the result on the Sunrise Control Panel after updating the front- |---|---| |serviceName|Your Load Balancer service ID| -## Go further +## Conclusion -You now have an infrastructure you can use to simply and efficiently manage `blue-green deployments`{.action}. +You have successfully implemented a highly available infrastructure for managing blue-green deployments. -Developers have access to a development environment on port 8888 (or whichever other port you would prefer to define), while your customers continue to access the service in production via the standard HTTP port (80 in our case, for example). +Developers have access to a development environment on port 8888 (or any configurable non-standard port), while your customers continue to access the service in production via the standard HTTP port (80). The infrastructure presented here is limited to just one port, but it can be expanded by adding other ports. For example, you can also expose your website on the standard HTTPS port (443). You can do this by defining new farms dedicated to each port you want to expose, and associating them with their corresponding front-ends (one for the standard port exposed in production, the second for the arbitrary port dedicated to development). Another way to consolidate your infrastructure even further is by multiplying the servers attached to your farms. This way, you can make your services more redundant (guaranteeing availability as a result), and also add a load balancing capacity. + +## Go further + +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/case_blue_green/guide.en-gb.md b/pages/network/load_balancer/case_blue_green/guide.en-gb.md index 9684209b85f..903379d1e2f 100644 --- a/pages/network/load_balancer/case_blue_green/guide.en-gb.md +++ b/pages/network/load_balancer/case_blue_green/guide.en-gb.md @@ -1,7 +1,7 @@ --- title: 'Deploying a blue-green infrastructure' excerpt: 'This guide will show you how to deploy a blue-green infrastructure with the OVHcloud Load Balancer' -updated: 2025-10-21 +updated: 2025-10-23 --- ## Objective @@ -18,7 +18,7 @@ To deploy a blue-green infrastructure, you need the following components: - An [OVHcloud Load Balancer](/links/network/load-balancer) service - Access to the [OVHcloud Control Panel](/links/manager) -- Two [dedicated servers](/links/bare-metal/bare-metal), one hosting your production environment, and a similarly configured server hosting your staging environment. +- Two [dedicated servers](/links/bare-metal/bare-metal), one hosting your production environment, and a similarly configured server hosting your staging environment ## Instructions @@ -38,7 +38,7 @@ In this scenario, your Load Balancer service plays a central role. It is the ele The production infrastructure can be accessed by your customers on the standard HTTP service (port 80), and your development infrastructure can be accessed by developers and admins on the non-standard port 8888. -During the initial setup phase, roles are provisionally assigned to each infrastructure component. **Infrastructure A** serves as the initial production environment, while **infrastructure B** serves as the staging environment. At this stage, we will consider them to be similar to one another. +During the initial setup phase, roles are provisionally assigned to each infrastructure component. **Infrastructure A** serves as the initial production environment, while **Infrastructure B** serves as the staging environment. At this stage, we will consider them to be similar to one another. A blue-green infrastructure involves switching from infrastructure A to infrastructure B, once infrastructure B has been fully updated and validated. The Load Balancer will manage this switch. @@ -56,7 +56,7 @@ In our scenario, we will declare a farm of servers for the HTTP service. Please ![Add a new HTTP farm dedicated to infrastructure A](images/ferme1.png){.thumbnail} -#### Via the API +#### Via the OVHcloud API > [!api] > @@ -279,7 +279,9 @@ This should be the result on the OVHcloud Control Panel after updating the front ![Result after updating front-ends](images/switch.png){.thumbnail} -#### Via the OVHcloud API: updating front-ends and applying modifications +#### Via the OVHcloud API + +- Updating front-ends and applying modifications: > [!api] > @@ -303,7 +305,7 @@ This should be the result on the OVHcloud Control Panel after updating the front |frontendId|Your production front-end ID|70090| |defaultFarmId|Your development server farm ID|77212| -#### To apply your changes and effectively switch over the production and development environments: +- To apply your changes and effectively switch over the production and development environments: > [!api] > @@ -326,4 +328,4 @@ Another way to consolidate your infrastructure even further is by multiplying th ## Go further -Join our [community of users](/links/community). +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/case_blue_green/guide.en-sg.md b/pages/network/load_balancer/case_blue_green/guide.en-sg.md index de705cecacc..903379d1e2f 100644 --- a/pages/network/load_balancer/case_blue_green/guide.en-sg.md +++ b/pages/network/load_balancer/case_blue_green/guide.en-sg.md @@ -1,64 +1,62 @@ --- title: 'Deploying a blue-green infrastructure' excerpt: 'This guide will show you how to deploy a blue-green infrastructure with the OVHcloud Load Balancer' -updated: 2019-02-25 +updated: 2025-10-23 --- ## Objective -With this guide, we will explore a specific use for the OVHcloud Load Balancer service — configuring a service to manage production/development infrastructures easily. This is also called a blue-green infrastructure. +This guide demonstrates a specific use case for the OVHcloud Load Balancer: the configuration of a service to facilitate seamless traffic switching between production and new production candidate environments, also called a **blue-green infrastructure**. -With a `blue-green`{.action} infrastructure, you can stop your infrastructure from experiencing any downtime. The main benefit of this deployment type is that you can prepare updates and/or maintenance in an environment that is isolated from your production environment. This way, you can test your changes before they are put into production, undo them quickly if you detect any faults, and do all of this with virtually zero downtime. +With a blue-green infrastructure, you can stop your infrastructure from experiencing any downtime. The main benefit of this deployment type is that you can prepare updates and/or maintenance in an environment that is isolated from your production environment. This way, you can test your changes before they are put into production, undo them quickly if you detect any faults, and do all of this with virtually zero downtime. **This guide will show you how to deploy a blue-green infrastructure with the OVHcloud Load Balancer.** ## Requirements -To deploy a `blue-green`{.action} infrastructure, you need the following components: +To deploy a blue-green infrastructure, you need the following components: -- an OVHcloud Load Balancer service -- a first server that hosts your production infrastructure -- a second server with a similar infrastructure, dedicated to development +- An [OVHcloud Load Balancer](/links/network/load-balancer) service +- Access to the [OVHcloud Control Panel](/links/manager) +- Two [dedicated servers](/links/bare-metal/bare-metal), one hosting your production environment, and a similarly configured server hosting your staging environment ## Instructions ### Scenario -The scenario we’ll describe here is as follows... +You have an infrastructure designed to host your live website. -You have an infrastructure that you can use to put your website online. +This environment hosts the website’s code, in addition to all essential applications (web servers, database servers, etc.). You need to update your applications and/or your code on a regular basis. You want to be able to test your updates without impacting the website's availability or functionality for end-users. -This infrastructure hosts your website’s code, and it also hosts the applications (web servers, database servers, etc.) required to put your website online. You need to update your applications and/or your code on a regular basis. You want to be able to test your updates without the risk of affecting your website’s availability to customers, or stopping the website from working properly. +One way to achieve this is by deploying a blue-green infrastructure. -One way to achieve this is by deploying a `blue-green`{.action} infrastructure. +The principle of a blue-green deployment involves being able to switch easily from a development infrastructure to a production infrastructure, and vice versa. This switch must be done in a way that is transparent for your users. To do this, public traffic will be routed to the standard HTTP port 80 for access to the production infrastructure, and a non-standard port, such as 8888, will be used to access the development infrastructure. -The principle of a `blue-green`{.action} deployment involves being able to switch easily from a development infrastructure to a production infrastructure, and vice versa. This switch must be done in a way that is transparent for your users. To do this, we will assign the standard HTTP port 80 for access to the production infrastructure, and the arbitrary port 8888 to access the development infrastructure. +## Deploy the infrastructures -## Deploy the infrastructures. - -In the scenario we are using, your IP Load Balancer service plays a central role. It is the element you use to expose your two infrastructures (production and development) to different users at the same time. +In this scenario, your Load Balancer service plays a central role. It is the element you use to expose your two infrastructures (production and development) to different users at the same time. The production infrastructure can be accessed by your customers on the standard HTTP service (port 80), and your development infrastructure can be accessed by developers and admins on the non-standard port 8888. -During the initial setup phase, we will arbitrarily assign a role to each of the parts of our infrastructure. `Infrastructure A`{.action} will be assigned to production, while `infrastructure B`{.action} will be assigned to development. At this stage, we will consider them to be similar to one another. +During the initial setup phase, roles are provisionally assigned to each infrastructure component. **Infrastructure A** serves as the initial production environment, while **Infrastructure B** serves as the staging environment. At this stage, we will consider them to be similar to one another. -A `blue-green`{.action} infrastructure involves switching from infrastructure A to infrastructure B, when infrastructure B is ready to expose your website after your changes have been applied and tested. The IP Load Balancer will manage this switch. +A blue-green infrastructure involves switching from infrastructure A to infrastructure B, once infrastructure B has been fully updated and validated. The Load Balancer will manage this switch. The diagram below gives a general idea of the architecture: ![General diagram of blue-green architecture](images/scheme.png){.thumbnail} -### Infrastructure A. +### Infrastructure A -This infrastructure is made up of a server farm that will later be associated with a front-end of your IP Load Balancer. This farm will expose an HTTP, TCP or UDP service to the front-end. It also balances loads by sending the front-end’s incoming traffic to the servers. For more detail on the role of various component of the OVHcloud Load Balancer service, you can read the following guide: [Introduction to the OVHcloud Load Balancer](/pages/network/load_balancer/use_presentation){.ref}. +This infrastructure is made up of a server farm that will later be associated with a front-end of your Load Balancer. This farm will expose an HTTP, TCP or UDP service to the front-end. It also balances loads by sending the front-end’s incoming traffic to the servers. For more details on the role of the various components of the OVHcloud Load Balancer service, please refer to the following guide: [Introduction to the OVHcloud Load Balancer](/pages/network/load_balancer/use_presentation). In our scenario, we will declare a farm of servers for the HTTP service. Please note that you can create as many farms (as well as TCP and/or UDP services) as are required for your final service to be exposed to your customers. -#### Via the OVHcloud Control Panel: +#### Via the OVHcloud Control Panel ![Add a new HTTP farm dedicated to infrastructure A](images/ferme1.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -69,7 +67,7 @@ In our scenario, we will declare a farm of servers for the HTTP service. Please |---|---| |serviceName|Your Load Balancer service ID| -With the additional calls listed below, you can list, modify and delete your server farms respectively. +With the additional calls listed below, you can list, modify and delete your server farms respectively: > [!api] > @@ -86,15 +84,15 @@ With the additional calls listed below, you can list, modify and delete your ser > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/http/farm > -Associate a server with your farm, if it is a physical server hosting your production infrastructure. The service exposed to the front-end is supplied by the server’s port 8080. Please note that you can associate one or more servers with each farm (to balance the load and/or offer higher fault tolerance, for ex.). +Link a dedicated server to your farm if it hosts your production infrastructure. The service is exposed to the front-end via the server’s port 8080. Note that you may LINK one or more servers with each farm (for example, to balance the load or offer higher fault tolerance). -#### Via the OVHcloud Control Panel: +#### Via the OVHcloud Control Panel ![Add a new server to the farm HTTP A](images/serveur1.png){.thumbnail} ![Enter the HTTP A server’s configuration](images/server1.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -109,7 +107,7 @@ Associate a server with your farm, if it is a physical server hosting your produ |displayName||The name of the server associated with your farm|HTTP A server| |port||The server port associated with your farm|8080| -With the additional calls listed below, you can list, modify and delete your servers respectively. +With the additional calls listed below, you can list, modify and delete your servers respectively: > [!api] > @@ -126,19 +124,19 @@ With the additional calls listed below, you can list, modify and delete your ser > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/http/farm/{farmId}/server > -### Infrastructure B. +### Infrastructure B -Functionally, this second infrastructure is identical to the first. It is also composed of a server farm that will later be associated with a second front-end of your IP Load Balancer. This server farm exposes the same service to the front-end as the first server farm. This service is supplied on the servers by port 8080. +Functionally, this second infrastructure is identical to the first. It is also composed of a server farm that will later be associated with a second front-end of your Load Balancer. This server farm exposes the same service to the front-end as the first server farm. This service is supplied on the servers by port 8080. Deploy the server farm for the HTTP service (and/or any other TCP or UDP services required for your final service to be exposed to your customers). -#### Via the Sunrise Control Panel: +#### Via the OVHcloud Control Panel ![Add a new HTTP farm dedicated to infrastructure B](images/ferme2.png){.thumbnail} ![Create a second farm dedicated to infrastructure B](images/backend2.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -151,13 +149,13 @@ Deploy the server farm for the HTTP service (and/or any other TCP or UDP service Associate a server with your farm. Here, it involves one or more physical servers hosting your development infrastructure. -#### Via the OVHcloud Control Panel: +#### Via the OVHcloud Control Panel ![Add a new server to the farm HTTP B](images/serveur2.png){.thumbnail} ![Enter the HTTP B server’s configuration](images/server2.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -176,9 +174,9 @@ At this stage, here is the configuration status for your two farms: ![Farm configuration](images/farms.png){.thumbnail} -## Front-ends. +## Front-ends -The magic of `blue-green`{.action} deployment lies in the configuration of your front-ends. At this stage, we have configure two functionally identical infrastructures. For both infrastructures, you have declared one or more server farms, each with their own set of associated servers. +The magic of blue-green deployment lies in the configuration of your front-ends. At this stage, we have configured two functionally identical infrastructures. For both infrastructures, you have declared one or more server farms, each with their own set of associated servers. To switch simply from one infrastructure to another, we will use front-ends. @@ -186,19 +184,20 @@ To do this, we need to declare two front-ends. The first one will give you acces > [!warning] > -> If the final service you expose to your customers requires several server farms (e.g. ports 80 and 443), you will need to declare a `front-end`{.action} for each of your farms. +> If the final service you expose to your customers requires several server farms (e.g. ports 80 and 443), you will need to declare a **front-end** for each of your farms. > -### Blue front-end. -This `front-end`{.action} is dedicated to accessing the production infrastructure. The ports exposed to your customers are the standard ports for accessing the service. In this case, we are exposing a HTTP service, so we will use port 80 (443 if you would like an SSL termination). +### Blue front-end + +This **front-end** is dedicated to accessing the production infrastructure. The ports exposed to your customers are the standard ports for accessing the service. In this case, we are exposing an HTTP service, so we will use port 80 (443 if you would like an SSL termination). -#### Via the OVHcloud Control Panel: +#### Via the OVHcloud Control Panel ![Adding a front-end dedicated to production, a blue front-end](images/frontend1.png){.thumbnail} ![Enter the blue front-end’s configuration](images/fblue.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -213,17 +212,17 @@ This `front-end`{.action} is dedicated to accessing the production infrastructur |port|Required|The port exposed to your customers by your front-end|80| |zone|Required|The zone in which you want to deploy your front-end|all| -### Green front-end. +### Green front-end -This `front-end`{.action} is dedicated to accessing the development infrastructure. The ports exposed to your customers will be non-standard ports that you can choose arbitrarily. In this case, we will expose the HTTP development service on port 8888. +This **front-end** is dedicated to accessing the development infrastructure. The ports exposed to your customers will be non-standard ports that you can choose arbitrarily. In this case, we will expose the HTTP development service on port 8888. -#### Via the OVHcloud Control Panel: +#### Via the OVHcloud Control Panel ![Add the green front-end, dedicated to development](images/frontend2.png){.thumbnail} ![Enter the green front-end’s configuration](images/fgreen.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -238,17 +237,17 @@ This `front-end`{.action} is dedicated to accessing the development infrastructu |port|Required|The port exposed to your customers by your front-end|8888| |zone|Required|The zone in which you want to deploy your front-end|all| -## Manage the deployments. +## Manage the deployments -### Initial deployment. +### Initial deployment -Once you have finished configuring the components of the OVHcloud Load Balancer service, you now just need to apply your changes. +Once you have finished configuring the components of the OVHcloud Load Balancer service, the only thing left to do is apply your changes. -#### Via the OVHcloud Control Panel: +#### Via the OVHcloud Control Panel ![Apply your changes to the zone](images/deploy.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -259,30 +258,30 @@ Once you have finished configuring the components of the OVHcloud Load Balancer |---|---| |serviceName|Your Load Balancer service ID| -### The production/pre-production switch. +### The production/staging switch -At this stage, our initial environment is deployed and ready to use. How do we use it? - -To put it simply, you just need to switch over your front-ends from one server farm to another. +At this stage, our initial environment is deployed and ready to use. Now, you need to switch over your front-ends from one server farm to another. Let’s take a look at our scenario: -- The production infrastructure (A) is deployed on `HTTP farm A`{.action} (id 77212), which in turn is attached to `HTTP server A`{.action}. This infrastructure can be accessed through the `blue front-end`{.action}. -- The development infrastructure (B) is deployed on `HTTP farm B`{.action} (id 77213), which in turn is attached to `HTTP server B`{.action}. This infrastructure can be accessed through the `green front-end`{.action}. +- The production infrastructure (A) is deployed on **HTTP farm A** (id 77212), which in turn is attached to **HTTP server A**. This infrastructure can be accessed through the **blue front-end**. +- The development infrastructure (B) is deployed on **HTTP farm B** (id 77213), which in turn is attached to **HTTP server B**. This infrastructure can be accessed through the **green front-end**. -Once you have modified/applied updates to `infrastructure B`{.action} and checked that the service is working properly, you decide to put it into production. +Once you have modified/applied updates to **infrastructure B** and checked that the service is working properly, you can decide to put it into production. To switch between the two farms, you can simply update your different front-ends by modifying the ID of the farm it is attached to, and applying the modification. -The `blue front-end`{.action} (id 70089) will then be associated with `Farm B`{.action} (infrastructure B, new production, id 77213). +The **blue front-end** (id 70089) will then be associated with **Farm B** (infrastructure B, new production, id 77213). -The `green front-end`{.action} (id 70090) will then be associated with `Farm A`{.action} (infrastructure A, new development, id 77212). +The **green front-end** (id 70090) will then be associated with **Farm A** (infrastructure A, new development, id 77212). -This should be the result on the Sunrise Control Panel after updating the front-ends and applying the new configuration: +This should be the result on the OVHcloud Control Panel after updating the front-ends and applying the new configuration: ![Result after updating front-ends](images/switch.png){.thumbnail} -#### Via the API: updating front-ends and applying modifications#### +#### Via the OVHcloud API + +- Updating front-ends and applying modifications: > [!api] > @@ -306,7 +305,7 @@ This should be the result on the Sunrise Control Panel after updating the front- |frontendId|Your production front-end ID|70090| |defaultFarmId|Your development server farm ID|77212| -#### To apply your changes and effectively switch over the production and development environments: +- To apply your changes and effectively switch over the production and development environments: > [!api] > @@ -317,12 +316,16 @@ This should be the result on the Sunrise Control Panel after updating the front- |---|---| |serviceName|Your Load Balancer service ID| -## Go further +## Conclusion -You now have an infrastructure you can use to simply and efficiently manage `blue-green deployments`{.action}. +You have successfully implemented a highly available infrastructure for managing blue-green deployments. -Developers have access to a development environment on port 8888 (or whichever other port you would prefer to define), while your customers continue to access the service in production via the standard HTTP port (80 in our case, for example). +Developers have access to a development environment on port 8888 (or any configurable non-standard port), while your customers continue to access the service in production via the standard HTTP port (80). The infrastructure presented here is limited to just one port, but it can be expanded by adding other ports. For example, you can also expose your website on the standard HTTPS port (443). You can do this by defining new farms dedicated to each port you want to expose, and associating them with their corresponding front-ends (one for the standard port exposed in production, the second for the arbitrary port dedicated to development). Another way to consolidate your infrastructure even further is by multiplying the servers attached to your farms. This way, you can make your services more redundant (guaranteeing availability as a result), and also add a load balancing capacity. + +## Go further + +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/case_blue_green/guide.en-us.md b/pages/network/load_balancer/case_blue_green/guide.en-us.md index de705cecacc..903379d1e2f 100644 --- a/pages/network/load_balancer/case_blue_green/guide.en-us.md +++ b/pages/network/load_balancer/case_blue_green/guide.en-us.md @@ -1,64 +1,62 @@ --- title: 'Deploying a blue-green infrastructure' excerpt: 'This guide will show you how to deploy a blue-green infrastructure with the OVHcloud Load Balancer' -updated: 2019-02-25 +updated: 2025-10-23 --- ## Objective -With this guide, we will explore a specific use for the OVHcloud Load Balancer service — configuring a service to manage production/development infrastructures easily. This is also called a blue-green infrastructure. +This guide demonstrates a specific use case for the OVHcloud Load Balancer: the configuration of a service to facilitate seamless traffic switching between production and new production candidate environments, also called a **blue-green infrastructure**. -With a `blue-green`{.action} infrastructure, you can stop your infrastructure from experiencing any downtime. The main benefit of this deployment type is that you can prepare updates and/or maintenance in an environment that is isolated from your production environment. This way, you can test your changes before they are put into production, undo them quickly if you detect any faults, and do all of this with virtually zero downtime. +With a blue-green infrastructure, you can stop your infrastructure from experiencing any downtime. The main benefit of this deployment type is that you can prepare updates and/or maintenance in an environment that is isolated from your production environment. This way, you can test your changes before they are put into production, undo them quickly if you detect any faults, and do all of this with virtually zero downtime. **This guide will show you how to deploy a blue-green infrastructure with the OVHcloud Load Balancer.** ## Requirements -To deploy a `blue-green`{.action} infrastructure, you need the following components: +To deploy a blue-green infrastructure, you need the following components: -- an OVHcloud Load Balancer service -- a first server that hosts your production infrastructure -- a second server with a similar infrastructure, dedicated to development +- An [OVHcloud Load Balancer](/links/network/load-balancer) service +- Access to the [OVHcloud Control Panel](/links/manager) +- Two [dedicated servers](/links/bare-metal/bare-metal), one hosting your production environment, and a similarly configured server hosting your staging environment ## Instructions ### Scenario -The scenario we’ll describe here is as follows... +You have an infrastructure designed to host your live website. -You have an infrastructure that you can use to put your website online. +This environment hosts the website’s code, in addition to all essential applications (web servers, database servers, etc.). You need to update your applications and/or your code on a regular basis. You want to be able to test your updates without impacting the website's availability or functionality for end-users. -This infrastructure hosts your website’s code, and it also hosts the applications (web servers, database servers, etc.) required to put your website online. You need to update your applications and/or your code on a regular basis. You want to be able to test your updates without the risk of affecting your website’s availability to customers, or stopping the website from working properly. +One way to achieve this is by deploying a blue-green infrastructure. -One way to achieve this is by deploying a `blue-green`{.action} infrastructure. +The principle of a blue-green deployment involves being able to switch easily from a development infrastructure to a production infrastructure, and vice versa. This switch must be done in a way that is transparent for your users. To do this, public traffic will be routed to the standard HTTP port 80 for access to the production infrastructure, and a non-standard port, such as 8888, will be used to access the development infrastructure. -The principle of a `blue-green`{.action} deployment involves being able to switch easily from a development infrastructure to a production infrastructure, and vice versa. This switch must be done in a way that is transparent for your users. To do this, we will assign the standard HTTP port 80 for access to the production infrastructure, and the arbitrary port 8888 to access the development infrastructure. +## Deploy the infrastructures -## Deploy the infrastructures. - -In the scenario we are using, your IP Load Balancer service plays a central role. It is the element you use to expose your two infrastructures (production and development) to different users at the same time. +In this scenario, your Load Balancer service plays a central role. It is the element you use to expose your two infrastructures (production and development) to different users at the same time. The production infrastructure can be accessed by your customers on the standard HTTP service (port 80), and your development infrastructure can be accessed by developers and admins on the non-standard port 8888. -During the initial setup phase, we will arbitrarily assign a role to each of the parts of our infrastructure. `Infrastructure A`{.action} will be assigned to production, while `infrastructure B`{.action} will be assigned to development. At this stage, we will consider them to be similar to one another. +During the initial setup phase, roles are provisionally assigned to each infrastructure component. **Infrastructure A** serves as the initial production environment, while **Infrastructure B** serves as the staging environment. At this stage, we will consider them to be similar to one another. -A `blue-green`{.action} infrastructure involves switching from infrastructure A to infrastructure B, when infrastructure B is ready to expose your website after your changes have been applied and tested. The IP Load Balancer will manage this switch. +A blue-green infrastructure involves switching from infrastructure A to infrastructure B, once infrastructure B has been fully updated and validated. The Load Balancer will manage this switch. The diagram below gives a general idea of the architecture: ![General diagram of blue-green architecture](images/scheme.png){.thumbnail} -### Infrastructure A. +### Infrastructure A -This infrastructure is made up of a server farm that will later be associated with a front-end of your IP Load Balancer. This farm will expose an HTTP, TCP or UDP service to the front-end. It also balances loads by sending the front-end’s incoming traffic to the servers. For more detail on the role of various component of the OVHcloud Load Balancer service, you can read the following guide: [Introduction to the OVHcloud Load Balancer](/pages/network/load_balancer/use_presentation){.ref}. +This infrastructure is made up of a server farm that will later be associated with a front-end of your Load Balancer. This farm will expose an HTTP, TCP or UDP service to the front-end. It also balances loads by sending the front-end’s incoming traffic to the servers. For more details on the role of the various components of the OVHcloud Load Balancer service, please refer to the following guide: [Introduction to the OVHcloud Load Balancer](/pages/network/load_balancer/use_presentation). In our scenario, we will declare a farm of servers for the HTTP service. Please note that you can create as many farms (as well as TCP and/or UDP services) as are required for your final service to be exposed to your customers. -#### Via the OVHcloud Control Panel: +#### Via the OVHcloud Control Panel ![Add a new HTTP farm dedicated to infrastructure A](images/ferme1.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -69,7 +67,7 @@ In our scenario, we will declare a farm of servers for the HTTP service. Please |---|---| |serviceName|Your Load Balancer service ID| -With the additional calls listed below, you can list, modify and delete your server farms respectively. +With the additional calls listed below, you can list, modify and delete your server farms respectively: > [!api] > @@ -86,15 +84,15 @@ With the additional calls listed below, you can list, modify and delete your ser > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/http/farm > -Associate a server with your farm, if it is a physical server hosting your production infrastructure. The service exposed to the front-end is supplied by the server’s port 8080. Please note that you can associate one or more servers with each farm (to balance the load and/or offer higher fault tolerance, for ex.). +Link a dedicated server to your farm if it hosts your production infrastructure. The service is exposed to the front-end via the server’s port 8080. Note that you may LINK one or more servers with each farm (for example, to balance the load or offer higher fault tolerance). -#### Via the OVHcloud Control Panel: +#### Via the OVHcloud Control Panel ![Add a new server to the farm HTTP A](images/serveur1.png){.thumbnail} ![Enter the HTTP A server’s configuration](images/server1.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -109,7 +107,7 @@ Associate a server with your farm, if it is a physical server hosting your produ |displayName||The name of the server associated with your farm|HTTP A server| |port||The server port associated with your farm|8080| -With the additional calls listed below, you can list, modify and delete your servers respectively. +With the additional calls listed below, you can list, modify and delete your servers respectively: > [!api] > @@ -126,19 +124,19 @@ With the additional calls listed below, you can list, modify and delete your ser > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/http/farm/{farmId}/server > -### Infrastructure B. +### Infrastructure B -Functionally, this second infrastructure is identical to the first. It is also composed of a server farm that will later be associated with a second front-end of your IP Load Balancer. This server farm exposes the same service to the front-end as the first server farm. This service is supplied on the servers by port 8080. +Functionally, this second infrastructure is identical to the first. It is also composed of a server farm that will later be associated with a second front-end of your Load Balancer. This server farm exposes the same service to the front-end as the first server farm. This service is supplied on the servers by port 8080. Deploy the server farm for the HTTP service (and/or any other TCP or UDP services required for your final service to be exposed to your customers). -#### Via the Sunrise Control Panel: +#### Via the OVHcloud Control Panel ![Add a new HTTP farm dedicated to infrastructure B](images/ferme2.png){.thumbnail} ![Create a second farm dedicated to infrastructure B](images/backend2.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -151,13 +149,13 @@ Deploy the server farm for the HTTP service (and/or any other TCP or UDP service Associate a server with your farm. Here, it involves one or more physical servers hosting your development infrastructure. -#### Via the OVHcloud Control Panel: +#### Via the OVHcloud Control Panel ![Add a new server to the farm HTTP B](images/serveur2.png){.thumbnail} ![Enter the HTTP B server’s configuration](images/server2.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -176,9 +174,9 @@ At this stage, here is the configuration status for your two farms: ![Farm configuration](images/farms.png){.thumbnail} -## Front-ends. +## Front-ends -The magic of `blue-green`{.action} deployment lies in the configuration of your front-ends. At this stage, we have configure two functionally identical infrastructures. For both infrastructures, you have declared one or more server farms, each with their own set of associated servers. +The magic of blue-green deployment lies in the configuration of your front-ends. At this stage, we have configured two functionally identical infrastructures. For both infrastructures, you have declared one or more server farms, each with their own set of associated servers. To switch simply from one infrastructure to another, we will use front-ends. @@ -186,19 +184,20 @@ To do this, we need to declare two front-ends. The first one will give you acces > [!warning] > -> If the final service you expose to your customers requires several server farms (e.g. ports 80 and 443), you will need to declare a `front-end`{.action} for each of your farms. +> If the final service you expose to your customers requires several server farms (e.g. ports 80 and 443), you will need to declare a **front-end** for each of your farms. > -### Blue front-end. -This `front-end`{.action} is dedicated to accessing the production infrastructure. The ports exposed to your customers are the standard ports for accessing the service. In this case, we are exposing a HTTP service, so we will use port 80 (443 if you would like an SSL termination). +### Blue front-end + +This **front-end** is dedicated to accessing the production infrastructure. The ports exposed to your customers are the standard ports for accessing the service. In this case, we are exposing an HTTP service, so we will use port 80 (443 if you would like an SSL termination). -#### Via the OVHcloud Control Panel: +#### Via the OVHcloud Control Panel ![Adding a front-end dedicated to production, a blue front-end](images/frontend1.png){.thumbnail} ![Enter the blue front-end’s configuration](images/fblue.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -213,17 +212,17 @@ This `front-end`{.action} is dedicated to accessing the production infrastructur |port|Required|The port exposed to your customers by your front-end|80| |zone|Required|The zone in which you want to deploy your front-end|all| -### Green front-end. +### Green front-end -This `front-end`{.action} is dedicated to accessing the development infrastructure. The ports exposed to your customers will be non-standard ports that you can choose arbitrarily. In this case, we will expose the HTTP development service on port 8888. +This **front-end** is dedicated to accessing the development infrastructure. The ports exposed to your customers will be non-standard ports that you can choose arbitrarily. In this case, we will expose the HTTP development service on port 8888. -#### Via the OVHcloud Control Panel: +#### Via the OVHcloud Control Panel ![Add the green front-end, dedicated to development](images/frontend2.png){.thumbnail} ![Enter the green front-end’s configuration](images/fgreen.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -238,17 +237,17 @@ This `front-end`{.action} is dedicated to accessing the development infrastructu |port|Required|The port exposed to your customers by your front-end|8888| |zone|Required|The zone in which you want to deploy your front-end|all| -## Manage the deployments. +## Manage the deployments -### Initial deployment. +### Initial deployment -Once you have finished configuring the components of the OVHcloud Load Balancer service, you now just need to apply your changes. +Once you have finished configuring the components of the OVHcloud Load Balancer service, the only thing left to do is apply your changes. -#### Via the OVHcloud Control Panel: +#### Via the OVHcloud Control Panel ![Apply your changes to the zone](images/deploy.png){.thumbnail} -#### Via the API: +#### Via the OVHcloud API > [!api] > @@ -259,30 +258,30 @@ Once you have finished configuring the components of the OVHcloud Load Balancer |---|---| |serviceName|Your Load Balancer service ID| -### The production/pre-production switch. +### The production/staging switch -At this stage, our initial environment is deployed and ready to use. How do we use it? - -To put it simply, you just need to switch over your front-ends from one server farm to another. +At this stage, our initial environment is deployed and ready to use. Now, you need to switch over your front-ends from one server farm to another. Let’s take a look at our scenario: -- The production infrastructure (A) is deployed on `HTTP farm A`{.action} (id 77212), which in turn is attached to `HTTP server A`{.action}. This infrastructure can be accessed through the `blue front-end`{.action}. -- The development infrastructure (B) is deployed on `HTTP farm B`{.action} (id 77213), which in turn is attached to `HTTP server B`{.action}. This infrastructure can be accessed through the `green front-end`{.action}. +- The production infrastructure (A) is deployed on **HTTP farm A** (id 77212), which in turn is attached to **HTTP server A**. This infrastructure can be accessed through the **blue front-end**. +- The development infrastructure (B) is deployed on **HTTP farm B** (id 77213), which in turn is attached to **HTTP server B**. This infrastructure can be accessed through the **green front-end**. -Once you have modified/applied updates to `infrastructure B`{.action} and checked that the service is working properly, you decide to put it into production. +Once you have modified/applied updates to **infrastructure B** and checked that the service is working properly, you can decide to put it into production. To switch between the two farms, you can simply update your different front-ends by modifying the ID of the farm it is attached to, and applying the modification. -The `blue front-end`{.action} (id 70089) will then be associated with `Farm B`{.action} (infrastructure B, new production, id 77213). +The **blue front-end** (id 70089) will then be associated with **Farm B** (infrastructure B, new production, id 77213). -The `green front-end`{.action} (id 70090) will then be associated with `Farm A`{.action} (infrastructure A, new development, id 77212). +The **green front-end** (id 70090) will then be associated with **Farm A** (infrastructure A, new development, id 77212). -This should be the result on the Sunrise Control Panel after updating the front-ends and applying the new configuration: +This should be the result on the OVHcloud Control Panel after updating the front-ends and applying the new configuration: ![Result after updating front-ends](images/switch.png){.thumbnail} -#### Via the API: updating front-ends and applying modifications#### +#### Via the OVHcloud API + +- Updating front-ends and applying modifications: > [!api] > @@ -306,7 +305,7 @@ This should be the result on the Sunrise Control Panel after updating the front- |frontendId|Your production front-end ID|70090| |defaultFarmId|Your development server farm ID|77212| -#### To apply your changes and effectively switch over the production and development environments: +- To apply your changes and effectively switch over the production and development environments: > [!api] > @@ -317,12 +316,16 @@ This should be the result on the Sunrise Control Panel after updating the front- |---|---| |serviceName|Your Load Balancer service ID| -## Go further +## Conclusion -You now have an infrastructure you can use to simply and efficiently manage `blue-green deployments`{.action}. +You have successfully implemented a highly available infrastructure for managing blue-green deployments. -Developers have access to a development environment on port 8888 (or whichever other port you would prefer to define), while your customers continue to access the service in production via the standard HTTP port (80 in our case, for example). +Developers have access to a development environment on port 8888 (or any configurable non-standard port), while your customers continue to access the service in production via the standard HTTP port (80). The infrastructure presented here is limited to just one port, but it can be expanded by adding other ports. For example, you can also expose your website on the standard HTTPS port (443). You can do this by defining new farms dedicated to each port you want to expose, and associating them with their corresponding front-ends (one for the standard port exposed in production, the second for the arbitrary port dedicated to development). Another way to consolidate your infrastructure even further is by multiplying the servers attached to your farms. This way, you can make your services more redundant (guaranteeing availability as a result), and also add a load balancing capacity. + +## Go further + +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/case_blue_green/guide.fr-ca.md b/pages/network/load_balancer/case_blue_green/guide.fr-ca.md index 8ac93e77b49..2fae96fee2c 100644 --- a/pages/network/load_balancer/case_blue_green/guide.fr-ca.md +++ b/pages/network/load_balancer/case_blue_green/guide.fr-ca.md @@ -1,54 +1,62 @@ --- -title: Infrastructure Blue-Green -excerpt: Cas pratique -updated: 2022-04-26 +title: "Déploiement d'une infrastructure blue-green" +excerpt: "Ce guide vous montre comment déployer une infrastructure blue-green avec le Load Balancer OVHcloud" +updated: 2025-10-23 --- -## Introduction -Avec ce guide nous vous proposons d'explorer un cas d'usage particulier de votre service OVHcloud Load Balancer : configurer son service pour gérer facilement une infrastructure production / développement également appelée Blue-Green. +## Objectif -## Déploiement Blue-Green -Un déploiement `Blue-Green`{.action} permet de s'affranchir du temps d'indisponibilité de votre infrastructure. L'intérêt principal est que ce type de déploiement vous offre la possibilité de préparer vos mises à jour et / ou maintenances dans un environnement isolé de votre environnement de production. Vous pouvez ainsi tester vos modifications avant leur mise en production mais aussi revenir rapidement en arrière en cas de détection d'un dysfonctionnement, tout ceci avec des délais d'indisponibilité quasiment nuls. +Ce guide présente un cas d'usage spécifique du service Load Balancer OVHcloud : la configuration d'un service visant à faciliter le basculement fluide du trafic entre l'environnement de production et un nouvel environnement candidat à la production, également appelé infrastructure **blue-green**. -### Prérequis -Pour mettre en oeuvre un déploiement de type `Blue-Green`{.action} vous devez disposer des éléments suivants : +Une infrastructure **blue-green** vous permet d'éviter toute interruption de service de votre infrastructure. Le principal avantage de ce type de déploiement est de pouvoir préparer des mises à jour et/ou des opérations de maintenance dans un environnement isolé de votre environnement de production. Vous pouvez ainsi tester vos modifications avant la mise en production, les annuler rapidement en cas de défaillance, et ce, avec une interruption de service quasi nulle. -- un service OVHcloud Load Balancer ; -- un premier serveur qui porte votre infrastructure de production ; -- un second serveur qui porte une infrastructure similaire dédiée au développement ; +**Ce guide vous montre comment déployer une infrastructure blue-green avec le Load Balancer OVHcloud.** + +## Prérequis + +Pour déployer une infrastructure **blue-green**, vous avez besoin des composants suivants : + +- Un service [Load Balancer OVHcloud](/links/network/load-balancer) +- Un accès à l'[espace client OVHcloud](/links/manager) +- Deux [serveurs dédiés](/links/bare-metal/bare-metal), l'un hébergeant votre environnement de production, l'autre, un serveur de configuration similaire hébergeant votre environnement de développement. + +## En pratique ### Scénario -Le scénario que nous vous proposons ici est le suivant : vous disposez d'une infrastructure qui vous permet de mettre en ligne votre site internet. -Cette infrastructure héberge le code de votre site mais aussi les applications (serveurs web, serveurs de base de données, etc.) nécessaires à la mise en ligne du site. Régulièrement vous êtes confronté à la nécessité de mettre à jour vos applications et / ou votre code. Vous souhaitez être en mesure de tester vos mises à jours sans impacter ni la disponibilité ni le bon fonctionnement du site exposé à vos clients. +Vous disposez d'une infrastructure conçue pour héberger votre site Web en direct. -Une solution possible pour atteindre ces objectifs est de mettre en œuvre un déploiement `Blue-Green`{.action}. +Cet environnement héberge le code de votre site Web, ainsi que toutes les applications essentielles (serveurs Web, serveurs de bases de données, etc.). Vous devez mettre à jour vos applications et/ou votre code régulièrement. Vous souhaitez pouvoir tester vos mises à jour sans impact sur la disponibilité ou la fonctionnalité du site Web pour les utilisateurs finaux. -Le principe d'un déploiement `Blue-Green`{.action} consiste à vous permettre de basculer facilement d'une infrastructure de développement vers une infrastructure de production, et vice-versa. Cette bascule doit pouvoir se faire de manière transparente pour vos différents utilisateurs. Pour ce faire nous allons assigner le port HTTP standard 80 pour les accès à l'infrastructure de production et le port arbitraire 8888 pour les accès à l'infrastructure de développement. +Une façon d'y parvenir est de déployer une infrastructure **blue-green**. -## Déployer les infrastructures -Dans le cadre du scénario proposé, votre service IP Load Balancing joue un rôle central. Il est l'élément qui vous permet d'exposer simultanément vos 2 infrastructures (production et développement) à vos différents utilisateurs. +Le principe d'un déploiement **blue-green** implique de pouvoir basculer facilement d'une infrastructure de développement à une infrastructure de production, et inversement. Ce basculement doit être transparent pour vos utilisateurs. Pour ce faire, le trafic public sera acheminé vers le port HTTP standard 80 pour l'accès à l'infrastructure de production, et un port non standard, tel que 8888, sera utilisé pour l'accès à l'infrastructure de développement. -L'infrastructure de production est accessible à vos clients sur le service HTTP standard (port 80). L'infrastructure de développement quant à elle est accessible à vos développeurs / administrateurs sur le port non-standard 8888. +## Déploiement des infrastructures -Durant la phase initiale d'installation, nous allons assigner arbitrairement un rôle à chacune des parties de notre infrastructure. L'`infrastructure A`{.action} sera assignée à la production tandis que l'`infrastructure B`{.action} sera assignée au développement. Nous considérerons qu'à ce stade elles sont similaires. +Dans ce scénario, votre service Load Balancer joue un rôle central. C'est l'élément que vous utilisez pour exposer simultanément vos deux infrastructures (production et développement) à différents utilisateurs. -Le déploiement `Blue-Green`{.action} consiste à basculer de l'infrastructure A vers l'infrastructure B lorsque cette dernière est prête à exposer votre site après que vos changements aient été appliqués et testés. C'est l'IPBL qui se chargera de gérer cette bascule. +L'infrastructure de production est accessible par vos clients sur le service HTTP standard (port 80), et votre infrastructure de développement est accessible par les développeurs et administrateurs sur le port non standard 8888. -Le schéma suivant détail l'architecture générale : +Au cours de la phase de configuration initiale, les rôles sont provisoirement attribués à chaque composant de l'infrastructure. **L'infrastructure A** sert d'environnement de production initial, tandis que **l'infrastructure B** sert d'environnement de staging. À ce stade, nous allons les considérer comme similaires l'une à l'autre. -![Schéma général de l'architecture blue-green](images/scheme.png){.thumbnail} +Une infrastructure **blue-green** implique le basculement de l'infrastructure A vers l'infrastructure B, une fois que l'infrastructure B est prête à exposer votre site Web après que vos modifications ont été appliquées et testées. Le Load Balancer gérera ce basculement. + +Le schéma ci-dessous donne une idée générale de l'architecture : + +![General diagram of blue-green architecture](images/scheme.png){.thumbnail} ### Infrastructure A -Cette infrastructure est composée d'une ferme de serveurs qui sera ultérieurement associée à un frontend de votre IPLB. Cette ferme expose au frontend un service de type HTTP, TCP ou UDP. Elle se charge également de la répartition de charge en transmettant aux serveurs le trafic reçu par le frontend. Pour plus de précision sur le rôle des différents éléments du service OVHcloud Load Balancer, vous pouvez vous réferer à cette documentation : [Présentation de l'OVH Load Balancer](/pages/network/load_balancer/use_presentation). -Dans le cadre de notre scénario, nous déclarons une ferme de serveurs pour le service HTTP. A noter que vous pouvez créer autant de fermes que de services TCP et / ou UDP nécessaires au bon fonctionnement du service final exposé à vos clients. +Cette infrastructure est composée d'une ferme de serveurs qui sera associée plus tard à un front-end de votre Load Balancer. Cette ferme exposera un service HTTP, TCP ou UDP au front-end. Elle assure également l'équilibrage de charge en envoyant le trafic entrant du front-end aux serveurs. Pour plus de détails sur le rôle des différents composants du service Load Balancer OVHcloud, vous pouvez lire le guide suivant : [Présentation du service OVHcloud Load Balancer ](/pages/network/load_balancer/use_presentation). -Depuis le manager : +Dans notre scénario, nous allons déclarer une ferme de serveurs pour le service HTTP. Veuillez noter que vous pouvez créer autant de fermes (ainsi que de services TCP et/ou UDP) que nécessaire pour que votre service final soit accessible à vos clients. -![Ajout d'une nouvelle ferme HTTP dédié à l'infrastructure A](images/ferme1.png){.thumbnail} +#### Via l'espace client OVHcloud -Via l'Api : +![Add a new HTTP farm dedicated to infrastructure A](images/ferme1.png){.thumbnail} + +#### Via l'API OVHcloud > [!api] > @@ -57,9 +65,9 @@ Via l'Api : |Paramètre|Signification| |---|---| -|serviceName|L'identifiant de votre service Load Balancer| +|serviceName|Votre ID de service Load Balancer| -Les appels complémentaires suivants vous permettront respectivement de lister, modifier ou supprimer vos fermes. +Avec les appels supplémentaires listés ci-dessous, vous pouvez respectivement lister, modifier et supprimer vos fermes de serveurs: > [!api] > @@ -76,15 +84,15 @@ Les appels complémentaires suivants vous permettront respectivement de lister, > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/http/farm > -Associer un serveur à votre ferme, il s'agit ici du serveur physique portant votre infrastructure de production. Le service exposé au frontend est fournis par le port 8080 du serveur. A noter que vous pouvez associer à chaque ferme un ou plusieurs serveurs (pour par exemple répartir la charge et / ou offrir une meilleur tolérance aux pannes). +Associez un **serveur dédié** à votre ferme s'il héberge votre infrastructure de production. Le service est exposé au front-end via le port 8080 du serveur. Notez que vous pouvez associer un ou plusieurs serveurs à chaque ferme (par exemple, pour équilibrer la charge ou offrir une tolérance aux pannes plus élevée). -Depuis le manager : +#### Via l'espace client OVHcloud -![Ajout d'un nouveau serveur à la ferme HTTP A](images/serveur1.png){.thumbnail} +![Add a new server to the farm HTTP A](images/serveur1.png){.thumbnail} -![Renseigner la configuration du serveur HTTP A](images/server1.png){.thumbnail} +![Enter the HTTP A server’s configuration](images/server1.png){.thumbnail} -Via l'Api : +#### Via l'API OVHcloud > [!api] > @@ -93,13 +101,13 @@ Via l'Api : |Paramètre|Requis|Signification|Exemple| |---|---|---|---| -|serviceName|Requis|L'identifiant de votre service Load Balancer|loadbalancer-abcdef0123456789| -|farmId|Requis|L'identifiant de votre ferme de serveurs|77212| -|address|Requis|L'addresse IPv4 de votre serveur|10.10.1.100| -|displayName||Le nom du serveur associé à votre ferme|Serveur HTTP A| +|serviceName|Requis|Votre ID de service Load Balancer|loadbalancer-abcdef0123456789| +|farmId|Requis|Votre ID de ferme de serveurs|77212| +|address|Requis|L'adresse IPv4 de votre serveur|10.10.1.100| +|displayName||Le nom du serveur associé à votre ferme|HTTP A server| |port||Le port du serveur associé à votre ferme|8080| -Les appels complémentaires suivants vous permettront respectivement de lister, modifier ou supprimer vos serveurs. +Avec les appels supplémentaires listés ci-dessous, vous pouvez respectivement lister, modifier et supprimer vos serveurs: > [!api] > @@ -117,17 +125,18 @@ Les appels complémentaires suivants vous permettront respectivement de lister, > ### Infrastructure B -Cette seconde infrastructure est fonctionnellement jumelle de la précédente, elle est également composée d'une ferme de serveurs qui sera ultérieurement associée à un second frontend de votre IPLB. Cette ferme expose au frontend le même service que la ferme précédemment créé. Ce service est fournis sur les serveurs par le port 8080. -Déployer la ferme de serveurs pour le service HTTP (et / ou tout autre service TCP ou UDP nécessaire au fonctionnement du service final exposé à vos clients). +Fonctionnellement, cette deuxième infrastructure est identique à la première. Elle est également composée d'une ferme de serveurs qui sera associée plus tard à un second front-end de votre Load Balancer. Cette ferme de serveurs expose le même service au front-end que la première ferme de serveurs. Ce service est fourni sur les serveurs par le port 8080. + +Déployez la ferme de serveurs pour le service HTTP (et/ou tout autre service TCP ou UDP requis pour que votre service final soit exposé à vos clients). -Depuis le manager Sunrise : +#### Via l'espace client OVHcloud -![Ajout d'une nouvelle ferme HTTP dédié à l'infrastructure B](images/ferme2.png){.thumbnail} +![Add a new HTTP farm dedicated to infrastructure B](images/ferme2.png){.thumbnail} -![Création d'une seconde ferme dédiée à l'infrastructure B](images/backend2.png){.thumbnail} +![Create a second farm dedicated to infrastructure B](images/backend2.png){.thumbnail} -Via l'Api : +#### Via l'API OVHcloud > [!api] > @@ -136,17 +145,17 @@ Via l'Api : |Paramètre|Signification| |---|---| -|serviceName|L'identifiant de votre service Load Balancer| +|serviceName|Votre ID de service Load Balancer| -Associer un serveur à votre ferme, il s'agit ici du (ou des) serveur(s) physique(s) portant votre infrastructure de développement. +Associez un serveur à votre ferme. Ici, il s'agit d'un ou plusieurs **serveurs dédiés** hébergeant votre infrastructure de développement. -Depuis le manager : +#### Via l'espace client OVHcloud -![Ajout d'une nouveau serveur à la ferme HTTP B](images/serveur2.png){.thumbnail} +![Add a new server to the farm HTTP B](images/serveur2.png){.thumbnail} -![Renseigner la configuration du serveur HTTP B](images/server2.png){.thumbnail} +![Enter the HTTP B server’s configuration](images/server2.png){.thumbnail} -Via l'Api : +#### Via l'API OVHcloud > [!api] > @@ -155,38 +164,40 @@ Via l'Api : |Paramètre|Requis|Signification|Exemple| |---|---|---|---| -|serviceName|Requis|L'identifiant de votre service Load Balancer|loadbalancer-abcdef0123456789| -|farmId|Requis|L'identifiant de votre ferme de serveurs|77213| -|address|Requis|L'addresse IPv4 de votre serveur|10.10.2.100| -|displayName||Le nom du serveur associé à votre ferme|Serveur HTTP B| +|serviceName|Requis|Votre ID de service Load Balancer|loadbalancer-abcdef0123456789| +|farmId|Requis|Votre ID de ferme de serveurs|77213| +|address|Requis|L'adresse IPv4 de votre serveur|10.10.2.100| +|displayName||Le nom du serveur associé à votre ferme|HTTP B server| |port||Le port du serveur associé à votre ferme|8080| -A ce stade voici l'état de la configuration de vos 2 fermes : +À ce stade, voici l'état de la configuration de vos deux fermes : -![Configuration des fermes](images/farms.png){.thumbnail} +![Farm configuration](images/farms.png){.thumbnail} -## Les frontends -Toute la magie du déploiement `Blue-Green`{.action} se situe au niveau de la configuration de vos frontends. A ce stade nous avons configuré 2 infrastructures fonctionnellement jumelles en déclarant, pour chaque infrastructure, une (ou plusieurs) ferme(s) de serveurs, avec pour chaque ferme son (ses) serveur(s) associé(s). +## Front-ends -Pour permettre de basculer simplement d'une infrastructure à une autre nous allons nous servir des frontends. +La magie du déploiement **blue-green** réside dans la configuration de vos front-ends. À ce stade, nous avons configuré deux infrastructures fonctionnellement identiques. Pour les deux infrastructures, vous avez déclaré une ou plusieurs fermes de serveurs, chacune avec son propre ensemble de serveurs associés. -Pour cela nous devons déclarer 2 frontends. Le premier permettra d'accéder à l'infrastructure de production tandis que le second se chargera des accès à l'infrastructure de développement. Les accès à l'une ou l'autre des infrastructures seront controlés grâce aux ports exposés à vos clients. +Pour basculer simplement d'une infrastructure à l'autre, nous utiliserons des front-ends. + +Pour ce faire, nous devons déclarer deux front-ends. Le premier vous donnera accès à votre infrastructure de production, tandis que le second vous donnera accès à votre infrastructure de développement. Vous pouvez contrôler l'accès à une infrastructure ou à l'autre en utilisant les ports que vous exposez à vos clients. > [!warning] > -> Si le service final exposé à vos clients nécessite plusieurs fermes de serveurs (par exemple : les ports 80 et 443), vous devrez déclarer un `frontend`{.action} pour chacune de vos fermes. +> Si le service final que vous exposez à vos clients nécessite plusieurs fermes de serveurs (par ex. les ports 80 et 443), vous devrez déclarer un **front-end** pour chacune de vos fermes. > -### Frontend Blue -Ce `frontend`{.action} est dédié aux accès à l'infrastructure de production, les ports exposés à vos clients sont les ports standards d'accès au service. Dans le cas présent nous exposons un service HTTP, nous allons donc utiliser le port 80 (443 si vous souhaitez une terminaison SSL). +### Front-end Blue + +Ce **front-end** est dédié à l'accès à l'infrastructure de production. Les ports exposés à vos clients sont les ports standard pour l'accès au service. Dans ce cas, nous exposons un service HTTP, nous utiliserons donc le port 80 (443 si vous souhaitez une terminaison SSL). -Depuis le manager : +#### Via l'espace client OVHcloud -![Ajout du frontend dédié à la production, Blue Frontend](images/frontend1.png){.thumbnail} +![Adding a front-end dedicated to production, a blue front-end](images/frontend1.png){.thumbnail} -![Renseigner la configuration du frontend Blue](images/fblue.png){.thumbnail} +![Enter the blue front-end’s configuration](images/fblue.png){.thumbnail} -Via l'Api : +#### Via l'API OVHcloud > [!api] > @@ -195,22 +206,23 @@ Via l'Api : |Paramètre|Requis|Signification|Exemple| |---|---|---|---| -|serviceName|Requis|L'identifiant de votre Load Balancer|loadbalancer-abcdef0123456789| -|defaultFarmId||L'identifiant de la ferme de production|77212| -|displayName||Le nom donné au frontend|Blue Frontend| -|port|Requis|Le port exposé par votre frontend à vos clients|80| -|zone|Requis|La zone dans laquelle vous souhaitez déployer votre frontend|all| +|serviceName|Requis|Votre ID de service Load Balancer|loadbalancer-abcdef0123456789| +|defaultFarmId||Votre ID de ferme de production|77212| +|displayName||Le nom donné au front-end|Blue front-end| +|port|Requis|Le port exposé à vos clients par votre front-end|80| +|zone|Requis|La zone dans laquelle vous souhaitez déployer votre front-end|all| -### Frontend Green -Ce `frontend`{.action} est dédié aux accès à l'infrastructure de développement, les ports exposés à vos clients seront des ports non-standards que vous pouvez choisir arbitrairement. Dans le cas présent nous allons exposer le service HTTP de développement sur le port 8888. +### Front-end Green -Depuis le manager : +Ce **front-end** est dédié à l'accès à l'infrastructure de développement. Les ports exposés à vos clients seront des ports non standard que vous pourrez choisir arbitrairement. Dans ce cas, nous exposerons le service de développement HTTP sur le port 8888. -![Ajout du frontend dédié au développement, Green Frontend](images/frontend2.png){.thumbnail} +#### Via l'espace client OVHcloud -![Renseigner la configuration du frontend Green](images/fgreen.png){.thumbnail} +![Add the green front-end, dedicated to development](images/frontend2.png){.thumbnail} -Via l'Api : +![Enter the green front-end’s configuration](images/fgreen.png){.thumbnail} + +#### Via l'API OVHcloud > [!api] > @@ -219,22 +231,23 @@ Via l'Api : |Paramètre|Requis|Signification|Exemple| |---|---|---|---| -|serviceName|Requis|L'identifiant de votre Load Balancer|loadbalancer-abcdef0123456789| -|defaultFarmId||L'identifiant de la ferme de production|77213| -|displayName||Le nom donné au frontend|Green Frontend| -|port|Requis|Le port exposé par votre frontend à vos clients|8888| -|zone|Requis|La zone dans laquelle vous souhaitez déployer votre frontend|all| +|serviceName|Requis|Votre ID de service Load Balancer|loadbalancer-abcdef0123456789| +|defaultFarmId||Votre ID de ferme de production|77213| +|displayName||Le nom donné au front-end|Green front-end| +|port|Requis|Le port exposé à vos clients par votre front-end|8888| +|zone|Requis|La zone dans laquelle vous souhaitez déployer votre front-end|all| -## Gérer les déploiements +## Gestion des déploiements ### Déploiement initial -Après avoir finalisé la configuration des différents composants de votre service OVHcloud Load Balancer, il ne vous reste plus qu'à appliquer vos changements. -Depuis le manager : +Une fois que vous avez terminé de configurer les composants du service Load Balancer OVHcloud, il ne vous reste plus qu'à appliquer vos modifications. + +#### Via l'espace client OVHcloud -![Appliquer vos changements sur la zone](images/deploy.png){.thumbnail} +![Apply your changes to the zone](images/deploy.png){.thumbnail} -Via l'Api : +#### Via l'API OVHcloud > [!api] > @@ -243,31 +256,30 @@ Via l'Api : |Paramètre|Signification| |---|---| -|serviceName|L'identifiant de votre service Load Balancer| +|serviceName|Votre ID de service Load Balancer| -### Bascule production / preproduction -À ce stade notre environnement initial est déployé et prêt à être utilisé. Comment l'utiliser ? +### Changement de production ou de mise en scène -De manière assez simple finalement, il suffira désormais de basculer vos frontends d'une ferme de serveur à une autre ! +À ce stade, notre environnement initial est déployé et prêt à l'emploi. Maintenant, vous devez basculer vos front-ends d'une ferme de serveurs à une autre. -Reprenons notre scénario : +Prenons notre scénario : -- l'infrastructure de production (A) est déployée sur la `Ferme HTTP A`{.action} (id 77212) qui est elle même attachée au `Serveur HTTP A`{.action}. L'accès à cette infrastructure se fait par l'intermédiaire du `Frontend Blue`{.action}. -- l'infrastructure de développement (B) est déployée sur la `Ferme HTTP B`{.action} (id 77213) qui est elle même attachée au `Serveur HTTP B`{.action}. L'accès à cette infrastructure se fait par l'intermédiaire du `Frontend Green`{.action}. +- L'infrastructure de production (A) est déployée sur la **ferme HTTP A** (id 77212), qui est elle-même attachée au **serveur HTTP A**. Cette infrastructure est accessible via le **front-end blue**. +- L'infrastructure de développement (B) est déployée sur la **ferme HTTP B** (id 77213), qui est elle-même attachée au **serveur HTTP B**. Cette infrastructure est accessible via le **front-end green**. -Après avoir réalisé vos modifications / mises à jours sur l'`infrastructure B`{.action} et validé le bon fonctionnement du service, vous décidez de l'assigner à la production. +Une fois que vous avez modifié/appliqué les mises à jour à l'**infrastructure B** et vérifié que le service fonctionne correctement, vous décidez de la mettre en production. -Pour faire la bascule entre les 2 fermes, il suffira simplement de mettre à jour vos différents frontends en modifiant l'identifiant de la ferme à laquelle ils sont rattachés et d'appliquer la modification. +Pour basculer entre les deux fermes, vous pouvez simplement mettre à jour vos différents front-ends en modifiant l'ID de la ferme à laquelle il est attaché, et en appliquant la modification. -Le `Frontend Blue`{.action} (id 70089) va donc être associé à la `Ferme B`{.action} (infrastructure B, nouvelle production, id 77213). +Le **front-end blue** (id 70089) sera alors associé à la **Ferme B** (infrastructure B, nouvelle production, id 77213). -Le `Frontend Green`{.action} (id 70090) quant à lui sera désormais associé à la `Ferme A`{.action} (infrastructure A, nouvelle développement, id 77212). +Le **front-end green** (id 70090) sera alors associé à la **Ferme A** (infrastructure A, nouveau développement, id 77212). -Résultat sur le manager Sunrise après mise à jour des frontends et application de la nouvelle configuration : +Voici le résultat attendu dans l'espace client OVHcloud après la mise à jour des front-ends et l'application de la nouvelle configuration : -![Résultat après la mise à jour des frontends](images/switch.png){.thumbnail} +![Result after updating front-ends](images/switch.png){.thumbnail} -Via l'Api : mise à jour des frontends et application des modifications +#### Via l'API OVHcloud : mise à jour des front-ends et application des modifications > [!api] > @@ -276,9 +288,9 @@ Via l'Api : mise à jour des frontends et application des modifications |Paramètre|Signification|Exemple| |---|---|---| -|ServiceName|L'identifiant de votre service Load Balancer|loadbalancer-abcdef0123456789| -|frontendId|L'identifiant de votre frontend de production|70089| -|defaultFarmId|L'identifiant de votre ferme de serveurs de développement|77213| +|serviceName|Votre ID de service Load Balancer|loadbalancer-abcdef0123456789| +|frontendId|Votre ID de front-end de production|70089| +|defaultFarmId|Votre ID de ferme de serveurs de développement|77213| > [!api] > @@ -287,11 +299,11 @@ Via l'Api : mise à jour des frontends et application des modifications |Paramètre|Signification|Exemple| |---|---|---| -|ServiceName|L'identifiant de votre service Load Balancer|loadbalancer-abcdef0123456789| -|frontendId|L'identifiant de votre frontend de production|70090| -|defaultFarmId|L'identifiant de votre ferme de serveurs de développement|77212| +|serviceName|Votre ID de service Load Balancer|loadbalancer-abcdef0123456789| +|frontendId|Votre ID de front-end de production|70090| +|defaultFarmId|Votre ID de ferme de serveurs de développement|77212| -Pour appliquer vos changements et réaliser effectivement la bascule production / développement. +#### Pour appliquer vos modifications et basculer effectivement les environnements de production et de développement > [!api] > @@ -300,13 +312,18 @@ Pour appliquer vos changements et réaliser effectivement la bascule production |Paramètre|Signification| |---|---| -|serviceName|L'identifiant de votre service Load Balancer| +|serviceName|Votre ID de service Load Balancer| ## Conclusion -Vous disposez désormais d'une infrastructure vous permettant de gérer simplement et efficacement vos déploiements `Blue-Green`{.action}. -Les développeurs disposent d'un accès à l'infrastructure de développement sur le port 8888 (ou tout autre port que vous auriez préférer définir) tandis que vos clients continuent d'accéder au service en production via le port HTTP standard (80 dans le cas de notre exemple). +Vous avez réussi à mettre en œuvre une infrastructure hautement disponible pour la gestion des déploiements blue-green. + +Les développeurs ont accès à un environnement de développement sur le port 8888 (ou tout port non standard configurable), tandis que vos clients continuent d'accéder au service en production via le port HTTP standard (80). + +L'infrastructure présentée ici est limitée à un seul port, mais elle peut être étendue en ajoutant d'autres ports. Par exemple, vous pouvez également exposer votre site Web sur le port HTTPS standard (443). Vous pouvez le faire en définissant de nouvelles fermes dédiées à chaque port que vous souhaitez exposer, et en les associant à leurs front-ends correspondants (un pour le port standard exposé en production, le second pour le port arbitraire dédié au développement). + +Une autre façon de consolider davantage votre infrastructure est de multiplier les serveurs attachés à vos fermes. De cette façon, vous pouvez rendre vos services plus redondants (garantissant ainsi la disponibilité) et ajouter également une capacité d'équilibrage de charge. -L'infrastructure présentée ici se limite à l'exposition d'un seul et unique port, elle peut bien entendue être développée en ajoutant d'autres ports. Vous pouvez par exemple vouloir également exposer votre site sur le port HTTPS standard (443). Ceci peut se faire en définissant de nouvelles fermes dédiées à chaque nouveau port que vous souhaitez exposer et en les associant à leurs frontends correspondant (un pour le port standard exposé en production, le second pour le port arbitraire dédié aux développements). +## Aller plus loin -Une autre possibilité pour consolider encore un peu plus votre infrastructure est de multiplier les serveurs attachés à votre (vos) ferme(s). Ceci vous permettra d'ajouter à la simplicité de réalisation de vos déploiements une redondance de vos services (garantissant ainsi leur disponibilité) ainsi qu'une capacité de répartition de charge. +Échangez avec notre [communauté d'utilisateurs](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/case_blue_green/guide.fr-fr.md b/pages/network/load_balancer/case_blue_green/guide.fr-fr.md index 87ee236d301..2fae96fee2c 100644 --- a/pages/network/load_balancer/case_blue_green/guide.fr-fr.md +++ b/pages/network/load_balancer/case_blue_green/guide.fr-fr.md @@ -1,7 +1,7 @@ --- title: "Déploiement d'une infrastructure blue-green" excerpt: "Ce guide vous montre comment déployer une infrastructure blue-green avec le Load Balancer OVHcloud" -updated: 2025-10-21 +updated: 2025-10-23 --- ## Objectif @@ -38,7 +38,7 @@ Dans ce scénario, votre service Load Balancer joue un rôle central. C'est l'é L'infrastructure de production est accessible par vos clients sur le service HTTP standard (port 80), et votre infrastructure de développement est accessible par les développeurs et administrateurs sur le port non standard 8888. -Au cours de la phase de configuration initiale, les rôles sont provisoirement attribués à chaque composant de l'infrastructure. **L'Infrastructure A** sert d'environnement de production initial, tandis que **l'infrastructure B** sert d'environnement de staging. À ce stade, nous allons les considérer comme similaires l'une à l'autre. +Au cours de la phase de configuration initiale, les rôles sont provisoirement attribués à chaque composant de l'infrastructure. **L'infrastructure A** sert d'environnement de production initial, tandis que **l'infrastructure B** sert d'environnement de staging. À ce stade, nous allons les considérer comme similaires l'une à l'autre. Une infrastructure **blue-green** implique le basculement de l'infrastructure A vers l'infrastructure B, une fois que l'infrastructure B est prête à exposer votre site Web après que vos modifications ont été appliquées et testées. Le Load Balancer gérera ce basculement. @@ -48,7 +48,7 @@ Le schéma ci-dessous donne une idée générale de l'architecture : ### Infrastructure A -Cette infrastructure est composée d'une ferme de serveurs qui sera associée plus tard à un front-end de votre Load Balancer. Cette ferme exposera un service HTTP, TCP ou UDP au front-end. Elle assure également l'équilibrage de charge en envoyant le trafic entrant du front-end aux serveurs. Pour plus de détails sur le rôle des différents composants du service Load Balancer OVHcloud, vous pouvez lire le guide suivant : [Introduction au Load Balancer OVHcloud](/pages/network/load_balancer/use_presentation). +Cette infrastructure est composée d'une ferme de serveurs qui sera associée plus tard à un front-end de votre Load Balancer. Cette ferme exposera un service HTTP, TCP ou UDP au front-end. Elle assure également l'équilibrage de charge en envoyant le trafic entrant du front-end aux serveurs. Pour plus de détails sur le rôle des différents composants du service Load Balancer OVHcloud, vous pouvez lire le guide suivant : [Présentation du service OVHcloud Load Balancer ](/pages/network/load_balancer/use_presentation). Dans notre scénario, nous allons déclarer une ferme de serveurs pour le service HTTP. Veuillez noter que vous pouvez créer autant de fermes (ainsi que de services TCP et/ou UDP) que nécessaire pour que votre service final soit accessible à vos clients. @@ -326,4 +326,4 @@ Une autre façon de consolider davantage votre infrastructure est de multiplier ## 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/create_balancing/guide.en-asia.md b/pages/network/load_balancer/create_balancing/guide.en-asia.md index 0d25c0f0aea..6236c3c22f6 100644 --- a/pages/network/load_balancer/create_balancing/guide.en-asia.md +++ b/pages/network/load_balancer/create_balancing/guide.en-asia.md @@ -1,105 +1,106 @@ --- title: Load balancing methods -excerpt: Find out about the various load balancing methods used by the OVH Load Balancer -updated: 2018-01-17 +excerpt: Discover the various load balancing algorithms available with the OVHcloud Load Balancer +updated: 2025-10-23 --- ## Objective -The new OVH Load Balancer service offers a variety of load balancing methods for your services. This process determines the way in which the OVH Load Balancer distributes the requests received by your servers. +The OVHcloud Load Balancer service supports a variety of load balancing algorithms for your services. This setting dictates how the Load Balancer distributes incoming client requests among the servers in a farm. -**This guide will provide an introduction to the various load balancing methods, and will explain how you can modify them.** +**This guide introduces the various load balancing methods and explains how to modify them.** ## Requirements -- You must be logged in to the [OVH Control Panel](/links/manager). +- An [OVHcloud Load Balancer](/links/network/load-balancer) service in your OVHcloud account. +- Access to the [OVHcloud Control Panel](/links/manager). - You need to have created a server farm. ## Instructions -### Different load balancing methods +### Available Load Balancing Algorithms -Load balancing is used in server farms. This setting defines the way that requests are distributed between the servers within the farm. +The load balancing setting is applied at the server farm level and defines the method by which client requests are distributed among the servers within that farm. -To understand the basics of the OVH Load Balancer service, please refer to the [Load Balancer Introduction](/pages/network/load_balancer/use_presentation). +For an overview of the OVHcloud Load Balancer service components, please refer to the [Load Balancer Introduction](/pages/network/load_balancer/use_presentation) guide. |Algorithm|Features| |---|---| -|First|The first available server receives the connection. The server is chosen according to its ID, from smallest to largest.| -|LeastConn|Selects the server that has the lowest number of active connections. This setting is recommended for long sessions, with low levels of traffic. The *RoundRobin* algorithm is applied to groups of servers that have the same number of active connections.| -|RoundRobin|Selects the servers one after the other for each connection. **This is the default algorithm.**| -|Source|This algorithm *hashes* the source IP address, then divides the result by the number of servers currently running. The same source IP address will then still be redirected to the same server, provided that it continues to run.| -|URI|This algorithm *hashes* part or all of the URI, then divides the result by the number of servers currently running. The same URI will then still be redirected to the same server, provided that it continues to run.| +|**First**|Directs the connection to the first available server based on its ID (smallest to largest).| +|**LeastConn**|Selects the server with the lowest number of active connections. This is recommended for long-duration sessions with light traffic. The *RoundRobin* algorithm is used for tie-breaking among equally loaded servers.| +|**RoundRobin**|Distributes connections sequentially, one after the other, for each new request. **This is the default algorithm.**| +|**Source**|Uses a hash of the source IP address to consistently redirect the same client IP to the same server, provided the server remains operational.| +|**URI**|Uses a hash of part or all of the URI path to consistently redirect identical URIs to the same server, provided the server remains operational. *(Applicable to HTTP/HTTPS farms only.)*| -### Modify a server farm’s load balancing method via the Control Panel +### Modify a server farm’s load balancing method via the OVHcloud Control Panel -- In the `Server farms`{.action} section (1), you will see the farms that have been created. You can edit them by clicking the three dots on the right-hand side (2), then `Change`{.action}: +- In the `Server farms`{.action} section (1), locate the desired farm. You can edit it by clicking the three dots on the right-hand side (2), then on `Change`{.action}. ![Modify a farm](images/server_cluster_change.png){.thumbnail} -In `Advanced settings`{.action}, you can modify your `Load balancing method`{.action}: +In `Advanced settings`{.action}, modify the `Load balancing method`{.action}. ![Modify a farm](images/distrib_mode_edit.png){.thumbnail} -Once you have selected your preferred load balancing method, click `Update`{.action}, then `Apply configuration`{.action} in the yellow banner that appears: +Once your preferred method is selected, click `Update`{.action}, then click `Apply configuration`{.action} in the yellow banner that appears. ![Apply configuration](images/apply_config.png){.thumbnail} -### Modify a server farm’s load balancing method via the API +### Modify a server farm’s load balancing method via the OVHcloud API -You can modify the load balancing method settings by editing them in the server farm. +The load balancing method is changed by updating the corresponding field within the server farm configuration. -- View details on a server farm +#### View details on a server farm -With this call instruction, you can view details on a server farm if you know its ID. In this example, we will work on an HTTP farm: +Use this api call to view the details of a server farm given its ID. In this example, we work with an HTTP farm: > [!api] > > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/http/farm/{farmId} -> +> |Setting|Meaning| |---|---| -|ServiceName*|Your Load Balancer service ID| +|serviceName*|Your Load Balancer service ID| |farmId*|The farm’s ID number| |Response (BackendHttp)|Meaning| |---|---| |farmId|The farm’s ID number| -|balance|Balance type currently set for the farm| +|balance|The load balancing algorithm currently set for the farm| |zone|Name of the zone in which the farm is configured| |port|Port used to contact the servers configured on the farm| |probe|Type of probe currently configured on the farm| |displayName|Name given to this farm| |stickiness|Connection monitoring method currently set for the farm| -- Modify a server farm’s load balancing method +#### Modify a server farm’s load balancing method -With this call instruction, you can edit the settings of a server farm if you know its ID. In this example, we will work on an HTTP farm. To modify the balancing method, the `BackendHttp.balance` field must be updated with an available balancing method: +Use this api call to edit the settings of a server farm given its ID. In this example, we work with an HTTP farm. To modify the balancing method, update the `BackendHttp.balance` field with an available algorithm: > [!api] > > @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/http/farm/{id} -> +> |Setting|Meaning| |---|---| -|ServiceName*|Your Load Balancer service ID| +|serviceName*|Your Load Balancer service ID| |farmId*|The farm’s ID number| |BackendHttp.balance|Preferred balancing method for this farm| -- Apply the modifications +#### Apply the modifications > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh -> +> |Setting|Meaning| |---|---| -|ServiceName*|Your Load Balancer service ID| +|serviceName*|Your Load Balancer service ID| |zone*|Name of the zone in which to deploy the configuration| ## Go further -Join our community of users on . +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/create_balancing/guide.en-au.md b/pages/network/load_balancer/create_balancing/guide.en-au.md index 0d25c0f0aea..6236c3c22f6 100644 --- a/pages/network/load_balancer/create_balancing/guide.en-au.md +++ b/pages/network/load_balancer/create_balancing/guide.en-au.md @@ -1,105 +1,106 @@ --- title: Load balancing methods -excerpt: Find out about the various load balancing methods used by the OVH Load Balancer -updated: 2018-01-17 +excerpt: Discover the various load balancing algorithms available with the OVHcloud Load Balancer +updated: 2025-10-23 --- ## Objective -The new OVH Load Balancer service offers a variety of load balancing methods for your services. This process determines the way in which the OVH Load Balancer distributes the requests received by your servers. +The OVHcloud Load Balancer service supports a variety of load balancing algorithms for your services. This setting dictates how the Load Balancer distributes incoming client requests among the servers in a farm. -**This guide will provide an introduction to the various load balancing methods, and will explain how you can modify them.** +**This guide introduces the various load balancing methods and explains how to modify them.** ## Requirements -- You must be logged in to the [OVH Control Panel](/links/manager). +- An [OVHcloud Load Balancer](/links/network/load-balancer) service in your OVHcloud account. +- Access to the [OVHcloud Control Panel](/links/manager). - You need to have created a server farm. ## Instructions -### Different load balancing methods +### Available Load Balancing Algorithms -Load balancing is used in server farms. This setting defines the way that requests are distributed between the servers within the farm. +The load balancing setting is applied at the server farm level and defines the method by which client requests are distributed among the servers within that farm. -To understand the basics of the OVH Load Balancer service, please refer to the [Load Balancer Introduction](/pages/network/load_balancer/use_presentation). +For an overview of the OVHcloud Load Balancer service components, please refer to the [Load Balancer Introduction](/pages/network/load_balancer/use_presentation) guide. |Algorithm|Features| |---|---| -|First|The first available server receives the connection. The server is chosen according to its ID, from smallest to largest.| -|LeastConn|Selects the server that has the lowest number of active connections. This setting is recommended for long sessions, with low levels of traffic. The *RoundRobin* algorithm is applied to groups of servers that have the same number of active connections.| -|RoundRobin|Selects the servers one after the other for each connection. **This is the default algorithm.**| -|Source|This algorithm *hashes* the source IP address, then divides the result by the number of servers currently running. The same source IP address will then still be redirected to the same server, provided that it continues to run.| -|URI|This algorithm *hashes* part or all of the URI, then divides the result by the number of servers currently running. The same URI will then still be redirected to the same server, provided that it continues to run.| +|**First**|Directs the connection to the first available server based on its ID (smallest to largest).| +|**LeastConn**|Selects the server with the lowest number of active connections. This is recommended for long-duration sessions with light traffic. The *RoundRobin* algorithm is used for tie-breaking among equally loaded servers.| +|**RoundRobin**|Distributes connections sequentially, one after the other, for each new request. **This is the default algorithm.**| +|**Source**|Uses a hash of the source IP address to consistently redirect the same client IP to the same server, provided the server remains operational.| +|**URI**|Uses a hash of part or all of the URI path to consistently redirect identical URIs to the same server, provided the server remains operational. *(Applicable to HTTP/HTTPS farms only.)*| -### Modify a server farm’s load balancing method via the Control Panel +### Modify a server farm’s load balancing method via the OVHcloud Control Panel -- In the `Server farms`{.action} section (1), you will see the farms that have been created. You can edit them by clicking the three dots on the right-hand side (2), then `Change`{.action}: +- In the `Server farms`{.action} section (1), locate the desired farm. You can edit it by clicking the three dots on the right-hand side (2), then on `Change`{.action}. ![Modify a farm](images/server_cluster_change.png){.thumbnail} -In `Advanced settings`{.action}, you can modify your `Load balancing method`{.action}: +In `Advanced settings`{.action}, modify the `Load balancing method`{.action}. ![Modify a farm](images/distrib_mode_edit.png){.thumbnail} -Once you have selected your preferred load balancing method, click `Update`{.action}, then `Apply configuration`{.action} in the yellow banner that appears: +Once your preferred method is selected, click `Update`{.action}, then click `Apply configuration`{.action} in the yellow banner that appears. ![Apply configuration](images/apply_config.png){.thumbnail} -### Modify a server farm’s load balancing method via the API +### Modify a server farm’s load balancing method via the OVHcloud API -You can modify the load balancing method settings by editing them in the server farm. +The load balancing method is changed by updating the corresponding field within the server farm configuration. -- View details on a server farm +#### View details on a server farm -With this call instruction, you can view details on a server farm if you know its ID. In this example, we will work on an HTTP farm: +Use this api call to view the details of a server farm given its ID. In this example, we work with an HTTP farm: > [!api] > > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/http/farm/{farmId} -> +> |Setting|Meaning| |---|---| -|ServiceName*|Your Load Balancer service ID| +|serviceName*|Your Load Balancer service ID| |farmId*|The farm’s ID number| |Response (BackendHttp)|Meaning| |---|---| |farmId|The farm’s ID number| -|balance|Balance type currently set for the farm| +|balance|The load balancing algorithm currently set for the farm| |zone|Name of the zone in which the farm is configured| |port|Port used to contact the servers configured on the farm| |probe|Type of probe currently configured on the farm| |displayName|Name given to this farm| |stickiness|Connection monitoring method currently set for the farm| -- Modify a server farm’s load balancing method +#### Modify a server farm’s load balancing method -With this call instruction, you can edit the settings of a server farm if you know its ID. In this example, we will work on an HTTP farm. To modify the balancing method, the `BackendHttp.balance` field must be updated with an available balancing method: +Use this api call to edit the settings of a server farm given its ID. In this example, we work with an HTTP farm. To modify the balancing method, update the `BackendHttp.balance` field with an available algorithm: > [!api] > > @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/http/farm/{id} -> +> |Setting|Meaning| |---|---| -|ServiceName*|Your Load Balancer service ID| +|serviceName*|Your Load Balancer service ID| |farmId*|The farm’s ID number| |BackendHttp.balance|Preferred balancing method for this farm| -- Apply the modifications +#### Apply the modifications > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh -> +> |Setting|Meaning| |---|---| -|ServiceName*|Your Load Balancer service ID| +|serviceName*|Your Load Balancer service ID| |zone*|Name of the zone in which to deploy the configuration| ## Go further -Join our community of users on . +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/create_balancing/guide.en-ca.md b/pages/network/load_balancer/create_balancing/guide.en-ca.md index 0d25c0f0aea..6236c3c22f6 100644 --- a/pages/network/load_balancer/create_balancing/guide.en-ca.md +++ b/pages/network/load_balancer/create_balancing/guide.en-ca.md @@ -1,105 +1,106 @@ --- title: Load balancing methods -excerpt: Find out about the various load balancing methods used by the OVH Load Balancer -updated: 2018-01-17 +excerpt: Discover the various load balancing algorithms available with the OVHcloud Load Balancer +updated: 2025-10-23 --- ## Objective -The new OVH Load Balancer service offers a variety of load balancing methods for your services. This process determines the way in which the OVH Load Balancer distributes the requests received by your servers. +The OVHcloud Load Balancer service supports a variety of load balancing algorithms for your services. This setting dictates how the Load Balancer distributes incoming client requests among the servers in a farm. -**This guide will provide an introduction to the various load balancing methods, and will explain how you can modify them.** +**This guide introduces the various load balancing methods and explains how to modify them.** ## Requirements -- You must be logged in to the [OVH Control Panel](/links/manager). +- An [OVHcloud Load Balancer](/links/network/load-balancer) service in your OVHcloud account. +- Access to the [OVHcloud Control Panel](/links/manager). - You need to have created a server farm. ## Instructions -### Different load balancing methods +### Available Load Balancing Algorithms -Load balancing is used in server farms. This setting defines the way that requests are distributed between the servers within the farm. +The load balancing setting is applied at the server farm level and defines the method by which client requests are distributed among the servers within that farm. -To understand the basics of the OVH Load Balancer service, please refer to the [Load Balancer Introduction](/pages/network/load_balancer/use_presentation). +For an overview of the OVHcloud Load Balancer service components, please refer to the [Load Balancer Introduction](/pages/network/load_balancer/use_presentation) guide. |Algorithm|Features| |---|---| -|First|The first available server receives the connection. The server is chosen according to its ID, from smallest to largest.| -|LeastConn|Selects the server that has the lowest number of active connections. This setting is recommended for long sessions, with low levels of traffic. The *RoundRobin* algorithm is applied to groups of servers that have the same number of active connections.| -|RoundRobin|Selects the servers one after the other for each connection. **This is the default algorithm.**| -|Source|This algorithm *hashes* the source IP address, then divides the result by the number of servers currently running. The same source IP address will then still be redirected to the same server, provided that it continues to run.| -|URI|This algorithm *hashes* part or all of the URI, then divides the result by the number of servers currently running. The same URI will then still be redirected to the same server, provided that it continues to run.| +|**First**|Directs the connection to the first available server based on its ID (smallest to largest).| +|**LeastConn**|Selects the server with the lowest number of active connections. This is recommended for long-duration sessions with light traffic. The *RoundRobin* algorithm is used for tie-breaking among equally loaded servers.| +|**RoundRobin**|Distributes connections sequentially, one after the other, for each new request. **This is the default algorithm.**| +|**Source**|Uses a hash of the source IP address to consistently redirect the same client IP to the same server, provided the server remains operational.| +|**URI**|Uses a hash of part or all of the URI path to consistently redirect identical URIs to the same server, provided the server remains operational. *(Applicable to HTTP/HTTPS farms only.)*| -### Modify a server farm’s load balancing method via the Control Panel +### Modify a server farm’s load balancing method via the OVHcloud Control Panel -- In the `Server farms`{.action} section (1), you will see the farms that have been created. You can edit them by clicking the three dots on the right-hand side (2), then `Change`{.action}: +- In the `Server farms`{.action} section (1), locate the desired farm. You can edit it by clicking the three dots on the right-hand side (2), then on `Change`{.action}. ![Modify a farm](images/server_cluster_change.png){.thumbnail} -In `Advanced settings`{.action}, you can modify your `Load balancing method`{.action}: +In `Advanced settings`{.action}, modify the `Load balancing method`{.action}. ![Modify a farm](images/distrib_mode_edit.png){.thumbnail} -Once you have selected your preferred load balancing method, click `Update`{.action}, then `Apply configuration`{.action} in the yellow banner that appears: +Once your preferred method is selected, click `Update`{.action}, then click `Apply configuration`{.action} in the yellow banner that appears. ![Apply configuration](images/apply_config.png){.thumbnail} -### Modify a server farm’s load balancing method via the API +### Modify a server farm’s load balancing method via the OVHcloud API -You can modify the load balancing method settings by editing them in the server farm. +The load balancing method is changed by updating the corresponding field within the server farm configuration. -- View details on a server farm +#### View details on a server farm -With this call instruction, you can view details on a server farm if you know its ID. In this example, we will work on an HTTP farm: +Use this api call to view the details of a server farm given its ID. In this example, we work with an HTTP farm: > [!api] > > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/http/farm/{farmId} -> +> |Setting|Meaning| |---|---| -|ServiceName*|Your Load Balancer service ID| +|serviceName*|Your Load Balancer service ID| |farmId*|The farm’s ID number| |Response (BackendHttp)|Meaning| |---|---| |farmId|The farm’s ID number| -|balance|Balance type currently set for the farm| +|balance|The load balancing algorithm currently set for the farm| |zone|Name of the zone in which the farm is configured| |port|Port used to contact the servers configured on the farm| |probe|Type of probe currently configured on the farm| |displayName|Name given to this farm| |stickiness|Connection monitoring method currently set for the farm| -- Modify a server farm’s load balancing method +#### Modify a server farm’s load balancing method -With this call instruction, you can edit the settings of a server farm if you know its ID. In this example, we will work on an HTTP farm. To modify the balancing method, the `BackendHttp.balance` field must be updated with an available balancing method: +Use this api call to edit the settings of a server farm given its ID. In this example, we work with an HTTP farm. To modify the balancing method, update the `BackendHttp.balance` field with an available algorithm: > [!api] > > @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/http/farm/{id} -> +> |Setting|Meaning| |---|---| -|ServiceName*|Your Load Balancer service ID| +|serviceName*|Your Load Balancer service ID| |farmId*|The farm’s ID number| |BackendHttp.balance|Preferred balancing method for this farm| -- Apply the modifications +#### Apply the modifications > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh -> +> |Setting|Meaning| |---|---| -|ServiceName*|Your Load Balancer service ID| +|serviceName*|Your Load Balancer service ID| |zone*|Name of the zone in which to deploy the configuration| ## Go further -Join our community of users on . +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/create_balancing/guide.en-gb.md b/pages/network/load_balancer/create_balancing/guide.en-gb.md index ec0383a9b82..6236c3c22f6 100644 --- a/pages/network/load_balancer/create_balancing/guide.en-gb.md +++ b/pages/network/load_balancer/create_balancing/guide.en-gb.md @@ -1,7 +1,7 @@ --- title: Load balancing methods excerpt: Discover the various load balancing algorithms available with the OVHcloud Load Balancer -updated: 2025-10-21 +updated: 2025-10-23 --- ## Objective @@ -22,7 +22,7 @@ The OVHcloud Load Balancer service supports a variety of load balancing algorith The load balancing setting is applied at the server farm level and defines the method by which client requests are distributed among the servers within that farm. -For an overview of the OVHcloud Load Balancer service components, please refer to the [Load Balancer Introduction](/pages/network/load_balancer/use_presentation). +For an overview of the OVHcloud Load Balancer service components, please refer to the [Load Balancer Introduction](/pages/network/load_balancer/use_presentation) guide. |Algorithm|Features| |---|---| @@ -34,7 +34,7 @@ For an overview of the OVHcloud Load Balancer service components, please refer t ### Modify a server farm’s load balancing method via the OVHcloud Control Panel -- In the `Server farms`{.action} section (1), locate the desired farm. You can edit it by clicking the three dots on the right-hand side (2), then `Change`{.action}. +- In the `Server farms`{.action} section (1), locate the desired farm. You can edit it by clicking the three dots on the right-hand side (2), then on `Change`{.action}. ![Modify a farm](images/server_cluster_change.png){.thumbnail} @@ -52,12 +52,12 @@ The load balancing method is changed by updating the corresponding field within #### View details on a server farm -Use this call to view the details of a server farm given its ID. In this example, we work with an HTTP farm: +Use this api call to view the details of a server farm given its ID. In this example, we work with an HTTP farm: > [!api] > > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/http/farm/{farmId} -> +> |Setting|Meaning| |---|---| @@ -76,12 +76,12 @@ Use this call to view the details of a server farm given its ID. In this example #### Modify a server farm’s load balancing method -Use this call to edit the settings of a server farm given its ID. In this example, we work with an HTTP farm. To modify the balancing method, update the `BackendHttp.balance` field with an available algorithm: +Use this api call to edit the settings of a server farm given its ID. In this example, we work with an HTTP farm. To modify the balancing method, update the `BackendHttp.balance` field with an available algorithm: > [!api] > > @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/http/farm/{id} -> +> |Setting|Meaning| |---|---| @@ -94,7 +94,7 @@ Use this call to edit the settings of a server farm given its ID. In this exampl > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh -> +> |Setting|Meaning| |---|---| @@ -103,4 +103,4 @@ Use this call to edit the settings of a server farm given its ID. In this exampl ## Go further -Join our [community of users](/links/community). +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/create_balancing/guide.en-sg.md b/pages/network/load_balancer/create_balancing/guide.en-sg.md index 0d25c0f0aea..6236c3c22f6 100644 --- a/pages/network/load_balancer/create_balancing/guide.en-sg.md +++ b/pages/network/load_balancer/create_balancing/guide.en-sg.md @@ -1,105 +1,106 @@ --- title: Load balancing methods -excerpt: Find out about the various load balancing methods used by the OVH Load Balancer -updated: 2018-01-17 +excerpt: Discover the various load balancing algorithms available with the OVHcloud Load Balancer +updated: 2025-10-23 --- ## Objective -The new OVH Load Balancer service offers a variety of load balancing methods for your services. This process determines the way in which the OVH Load Balancer distributes the requests received by your servers. +The OVHcloud Load Balancer service supports a variety of load balancing algorithms for your services. This setting dictates how the Load Balancer distributes incoming client requests among the servers in a farm. -**This guide will provide an introduction to the various load balancing methods, and will explain how you can modify them.** +**This guide introduces the various load balancing methods and explains how to modify them.** ## Requirements -- You must be logged in to the [OVH Control Panel](/links/manager). +- An [OVHcloud Load Balancer](/links/network/load-balancer) service in your OVHcloud account. +- Access to the [OVHcloud Control Panel](/links/manager). - You need to have created a server farm. ## Instructions -### Different load balancing methods +### Available Load Balancing Algorithms -Load balancing is used in server farms. This setting defines the way that requests are distributed between the servers within the farm. +The load balancing setting is applied at the server farm level and defines the method by which client requests are distributed among the servers within that farm. -To understand the basics of the OVH Load Balancer service, please refer to the [Load Balancer Introduction](/pages/network/load_balancer/use_presentation). +For an overview of the OVHcloud Load Balancer service components, please refer to the [Load Balancer Introduction](/pages/network/load_balancer/use_presentation) guide. |Algorithm|Features| |---|---| -|First|The first available server receives the connection. The server is chosen according to its ID, from smallest to largest.| -|LeastConn|Selects the server that has the lowest number of active connections. This setting is recommended for long sessions, with low levels of traffic. The *RoundRobin* algorithm is applied to groups of servers that have the same number of active connections.| -|RoundRobin|Selects the servers one after the other for each connection. **This is the default algorithm.**| -|Source|This algorithm *hashes* the source IP address, then divides the result by the number of servers currently running. The same source IP address will then still be redirected to the same server, provided that it continues to run.| -|URI|This algorithm *hashes* part or all of the URI, then divides the result by the number of servers currently running. The same URI will then still be redirected to the same server, provided that it continues to run.| +|**First**|Directs the connection to the first available server based on its ID (smallest to largest).| +|**LeastConn**|Selects the server with the lowest number of active connections. This is recommended for long-duration sessions with light traffic. The *RoundRobin* algorithm is used for tie-breaking among equally loaded servers.| +|**RoundRobin**|Distributes connections sequentially, one after the other, for each new request. **This is the default algorithm.**| +|**Source**|Uses a hash of the source IP address to consistently redirect the same client IP to the same server, provided the server remains operational.| +|**URI**|Uses a hash of part or all of the URI path to consistently redirect identical URIs to the same server, provided the server remains operational. *(Applicable to HTTP/HTTPS farms only.)*| -### Modify a server farm’s load balancing method via the Control Panel +### Modify a server farm’s load balancing method via the OVHcloud Control Panel -- In the `Server farms`{.action} section (1), you will see the farms that have been created. You can edit them by clicking the three dots on the right-hand side (2), then `Change`{.action}: +- In the `Server farms`{.action} section (1), locate the desired farm. You can edit it by clicking the three dots on the right-hand side (2), then on `Change`{.action}. ![Modify a farm](images/server_cluster_change.png){.thumbnail} -In `Advanced settings`{.action}, you can modify your `Load balancing method`{.action}: +In `Advanced settings`{.action}, modify the `Load balancing method`{.action}. ![Modify a farm](images/distrib_mode_edit.png){.thumbnail} -Once you have selected your preferred load balancing method, click `Update`{.action}, then `Apply configuration`{.action} in the yellow banner that appears: +Once your preferred method is selected, click `Update`{.action}, then click `Apply configuration`{.action} in the yellow banner that appears. ![Apply configuration](images/apply_config.png){.thumbnail} -### Modify a server farm’s load balancing method via the API +### Modify a server farm’s load balancing method via the OVHcloud API -You can modify the load balancing method settings by editing them in the server farm. +The load balancing method is changed by updating the corresponding field within the server farm configuration. -- View details on a server farm +#### View details on a server farm -With this call instruction, you can view details on a server farm if you know its ID. In this example, we will work on an HTTP farm: +Use this api call to view the details of a server farm given its ID. In this example, we work with an HTTP farm: > [!api] > > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/http/farm/{farmId} -> +> |Setting|Meaning| |---|---| -|ServiceName*|Your Load Balancer service ID| +|serviceName*|Your Load Balancer service ID| |farmId*|The farm’s ID number| |Response (BackendHttp)|Meaning| |---|---| |farmId|The farm’s ID number| -|balance|Balance type currently set for the farm| +|balance|The load balancing algorithm currently set for the farm| |zone|Name of the zone in which the farm is configured| |port|Port used to contact the servers configured on the farm| |probe|Type of probe currently configured on the farm| |displayName|Name given to this farm| |stickiness|Connection monitoring method currently set for the farm| -- Modify a server farm’s load balancing method +#### Modify a server farm’s load balancing method -With this call instruction, you can edit the settings of a server farm if you know its ID. In this example, we will work on an HTTP farm. To modify the balancing method, the `BackendHttp.balance` field must be updated with an available balancing method: +Use this api call to edit the settings of a server farm given its ID. In this example, we work with an HTTP farm. To modify the balancing method, update the `BackendHttp.balance` field with an available algorithm: > [!api] > > @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/http/farm/{id} -> +> |Setting|Meaning| |---|---| -|ServiceName*|Your Load Balancer service ID| +|serviceName*|Your Load Balancer service ID| |farmId*|The farm’s ID number| |BackendHttp.balance|Preferred balancing method for this farm| -- Apply the modifications +#### Apply the modifications > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh -> +> |Setting|Meaning| |---|---| -|ServiceName*|Your Load Balancer service ID| +|serviceName*|Your Load Balancer service ID| |zone*|Name of the zone in which to deploy the configuration| ## Go further -Join our community of users on . +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/create_balancing/guide.fr-ca.md b/pages/network/load_balancer/create_balancing/guide.fr-ca.md index 2f5e1657ebf..f88fe19a84e 100644 --- a/pages/network/load_balancer/create_balancing/guide.fr-ca.md +++ b/pages/network/load_balancer/create_balancing/guide.fr-ca.md @@ -1,39 +1,40 @@ --- -title: Mode de répartition -excerpt: Découvrez les différents modes de répartition de charge de l'OVH Load Balancer -updated: 2018-01-17 +title: Modes de répartition +excerpt: Découvrez les différents modes de répartition de charge du Load Balancer OVHcloud +updated: 2025-10-23 --- ## Objectif -Le nouveau service OVH Load Balancer offre différents types de répartition de charge pour vos services. Ce processus détermine la manière dont l'OVH Load Balancer va répartir les requêtes reçues vers vos serveurs. +Le service OVHcloud Load Balancer prend en charge différents algorithmes de répartition de charge pour vos services. Ce paramètre détermine la manière dont le Load Balancer va distribuer les requêtes clientes entrantes vers les serveurs d'une ferme. -**Ce guide vous présente les différents types de répartition de charge et vous explique comment les modifier.** +**Ce guide présente les différents algorithmes de répartition de charge et explique comment les modifier.** ## Prérequis -- Être connecté à l'[espace client OVH](/links/manager). +- Posséder une offre [OVHcloud Load balancer](/links/network/load-balancer) dans votre compte OVHcloud. +- Être connecté à votre [espace client OVHcloud](/links/manager) - Posséder une ferme de serveurs créée. ## En pratique -### Les différents types de répartition de charge +### Algorithmes de répartition de charge disponibles -La répartition de charge est utilisée dans les fermes de serveurs. C'est ce paramètre qui définit la manière dont les requêtes sont réparties entre les serveurs de la ferme. +L'algorithme de répartition de charge est appliqué au niveau des fermes de serveurs. C'est ce paramètre qui définit la manière dont les requêtes sont réparties entre les serveurs de la ferme. -Pour connaître les différentes parties élémentaires du service OVH Load Balancer, voir [Présentation Load Balancer](/pages/network/load_balancer/use_presentation). +Pour une vue d'ensemble des composants du service OVHcloud Load Balancer, consultez ce guide : [Présentation du service OVHcloud Load Balancer](/pages/network/load_balancer/use_presentation). |Algorithme|Fonctionnalités| |---|---| -|First|Le premier serveur disponible reçoit la connexion. Le serveur est choisi en fonction de son ID, du plus petit au plus grand.| -|LeastConn|Sélectionne le serveur qui a le moins de connexions actives, c'est le paramètre recommandé pour de longues sessions avec peu de trafic. L'algorithme *RoundRobin* est appliqué sur les groupes de serveurs qui ont le même nombre de connexion actives.| -|RoundRobin|Sélectionne les serveurs les uns après les autres pour chaque connexion, **c'est l'algorithme par défaut.**| -|Source|Cet algorithme effectue une fonction de *hashage* (hash) sur l'adresse IP source, puis divise le résultat par le nombre de serveurs actuellement actifs. La même adresse IP source sera alors toujours redirigée vers le même serveur, tant que celui-ci reste actif.| -|URI|Cet algorithme effectue une fonction de *hashage* (hash) sur une partie, ou sur l'URI entière, puis divise le résultat par le nombre de serveurs actuellement actifs. Le même URI sera alors toujours redirigée vers le même serveur tant, que celui-ci reste actif.| +|**First**|Dirige la connexion vers le premier serveur disponible en fonction de son ID (du plus petit au plus grand).| +|**LeastConn**|Sélectionne le serveur qui a le moins de connexions actives. Ceci est recommandé pour les sessions longues avec peu de trafic. L'algorithme *RoundRobin* est appliqué pour départager les serveurs ayant un nombre de connexions actives égal.| +|**RoundRobin**|Distribue les connexions séquentiellement, les unes après les autres, pour chaque nouvelle requête. **C'est l'algorithme par défaut.**| +|**Source**|Utilise une fonction de *hachage* sur l'adresse IP source pour rediriger systématiquement la même IP cliente vers le même serveur, tant que celui-ci reste opérationnel.| +|**URI**|Utilise une fonction de *hachage* sur une partie ou la totalité de l'URI pour rediriger systématiquement les URI identiques vers le même serveur, tant que celui-ci reste opérationnel. *(Applicable uniquement aux fermes HTTP/HTTPS.)*| -### Modifier le mode de répartition de charge d'une ferme via l'espace client +### Modifier l'algorithme de répartition de charge d'une ferme via l'espace client OVHcloud -- Dans la section `Fermes de serveur`{.action} (1) vous verrez les fermes actuellement créées. Il vous suffit d'éditer l'une d'entre elles en cliquant sur les trois points à droite (2) puis `Modifier`{.action} : +Dans la section `Fermes de serveur`{.action}, vous verrez les fermes actuellement créées. Il vous suffit d'éditer l'une d'entre elles en cliquant sur les trois points à droite puis sur `Modifier`{.action} : ![Modification d'une ferme](images/server_cluster_change.png){.thumbnail} @@ -41,65 +42,65 @@ Dans les `Paramètres avancés`{.action} vous pourrez modifier votre `Mode de r ![Modification d'une ferme](images/distrib_mode_edit.png){.thumbnail} -Une fois le mode de répartition souhaité sélectionné, cliquez sur `Mettre à jour`{.action}, puis sur `Appliquer la configuration`{.action} dans le bandeau jaune qui apparaît : +Une fois l'algorithme souhaité sélectionné, cliquez sur `Mettre à jour`{.action}, puis sur `Appliquer la configuration`{.action} dans le bandeau jaune qui apparaît : ![Appliquer la configuration](images/apply_config.png){.thumbnail} -### Modifier le mode de répartition de charge d'une ferme via l'API +### Modifier l'algorithme de répartition de charge d'une ferme depuis l'API OVHcloud -La modification des paramètres de mode de répartition s'effectue en éditant ceux de la ferme de serveurs. +La modification de l'algorithme de répartition s'effectue en éditant le champ correspondant dans la configuration de la ferme de serveurs. -- Voir le détail d'une ferme +#### Voir le détail d'une ferme -Cet appel permet de consulter le détail d'une ferme en connaissant son identifiant. Dans cet exemple, nous allons travailler sur une ferme HTTP : +Cet appel API permet de consulter le détail d'une ferme en connaissant son identifiant. Dans cet exemple, nous travaillons sur une ferme HTTP : > [!api] > > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/http/farm/{farmId} -> +> |Paramètre|Signification| |---|---| -|ServiceName\*|Identifiant de votre service Load Balancer| -|farmId\*|Identifiant numérique de la ferme| +|serviceName*|Identifiant de votre service Load Balancer| +|farmId*|Identifiant numérique de la ferme| |Réponse (BackendHttp)|Signification| |---|---| |farmId|Identifiant numérique de la ferme| -|balance|Type de répartition actuellement configuré sur la ferme| +|balance|Algorithme de répartition de charge actuellement configuré sur la ferme| |zone|Nom de la zone où est configurée la ferme| -|port|port utilisé pour contacter les serveurs configurés sur la ferme| +|port|Port utilisé pour contacter les serveurs configurés sur la ferme| |probe|Type de sonde actuellement configurée sur la ferme| |displayName|Nom donné à cette ferme| |stickiness|Mode de suivi de connexion actuellement configuré sur la ferme| -- Modifier le mode de répartition d'une ferme +#### Modifier l'algorithme de répartition de charge d'une ferme -Cet appel permet de modifier la configuration d'une ferme en connaissant son identifiant. Dans cet exemple, nous allons travailler sur une ferme HTTP. Pour modifier le mode de répartition, le champ `BackendHttp.balance` doit être mis à jour avec un mode de répartition disponible : +Cet appel API permet de modifier la configuration d'une ferme en connaissant son identifiant. Dans cet exemple, nous travaillons sur une ferme HTTP. Pour modifier le mode de répartition, le champ `BackendHttp.balance` doit être mis à jour avec un algorithme disponible : > [!api] > > @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/http/farm/{id} -> +> |Paramètre|Signification| |---|---| -|ServiceName\*|Identifiant de votre service Load Balancer| -|farmId\*|Identifiant numérique de la ferme| -|BackendHttp.balance|Type de répartition souhaité pour cette ferme| +|serviceName*|Identifiant de votre service Load Balancer| +|farmId*|Identifiant numérique de la ferme| +|BackendHttp.balance|Algorithme de répartition souhaité pour cette ferme| -- Appliquer les modifications +#### Appliquer les modifications > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh -> +> |Paramètre|Signification| |---|---| -|ServiceName\*|Identifiant de votre service Load Balancer| -|zone\*|Nom de la zone dans laquelle déployer la configuration| +|serviceName*|Identifiant de votre service Load Balancer| +|zone*|Nom de la zone dans laquelle déployer la configuration| ## 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/create_balancing/guide.fr-fr.md b/pages/network/load_balancer/create_balancing/guide.fr-fr.md index 8f3b7f9aed3..f88fe19a84e 100644 --- a/pages/network/load_balancer/create_balancing/guide.fr-fr.md +++ b/pages/network/load_balancer/create_balancing/guide.fr-fr.md @@ -1,7 +1,7 @@ --- title: Modes de répartition excerpt: Découvrez les différents modes de répartition de charge du Load Balancer OVHcloud -updated: 2025-10-21 +updated: 2025-10-23 --- ## Objectif @@ -22,7 +22,7 @@ Le service OVHcloud Load Balancer prend en charge différents algorithmes de ré L'algorithme de répartition de charge est appliqué au niveau des fermes de serveurs. C'est ce paramètre qui définit la manière dont les requêtes sont réparties entre les serveurs de la ferme. -Pour une vue d'ensemble des composants du service OVHcloud Load Balancer, consultez la [présentation du Load Balancer](/pages/network/load_balancer/use_presentation). +Pour une vue d'ensemble des composants du service OVHcloud Load Balancer, consultez ce guide : [Présentation du service OVHcloud Load Balancer](/pages/network/load_balancer/use_presentation). |Algorithme|Fonctionnalités| |---|---| @@ -57,7 +57,7 @@ Cet appel API permet de consulter le détail d'une ferme en connaissant son iden > [!api] > > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/http/farm/{farmId} -> +> |Paramètre|Signification| |---|---| @@ -81,7 +81,7 @@ Cet appel API permet de modifier la configuration d'une ferme en connaissant son > [!api] > > @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/http/farm/{id} -> +> |Paramètre|Signification| |---|---| @@ -94,7 +94,7 @@ Cet appel API permet de modifier la configuration d'une ferme en connaissant son > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh -> +> |Paramètre|Signification| |---|---| @@ -103,4 +103,4 @@ Cet appel API permet de modifier la configuration d'une ferme en connaissant son ## Aller plus loin -Échangez avec notre [communauté d'utilisateurs](/links/community). +Échangez avec notre [communauté d'utilisateurs](/links/community). \ No newline at end of file From 3127da8554a772c019d5c74cc3ffb79be218e33e Mon Sep 17 00:00:00 2001 From: jessica Date: Thu, 23 Oct 2025 18:14:33 -0400 Subject: [PATCH 20/23] adding missing files --- .../create_balancing/guide.en-ie.md | 106 ++++++++++++++++++ .../create_balancing/guide.en-us.md | 106 ++++++++++++++++++ 2 files changed, 212 insertions(+) create mode 100644 pages/network/load_balancer/create_balancing/guide.en-ie.md create mode 100644 pages/network/load_balancer/create_balancing/guide.en-us.md diff --git a/pages/network/load_balancer/create_balancing/guide.en-ie.md b/pages/network/load_balancer/create_balancing/guide.en-ie.md new file mode 100644 index 00000000000..6236c3c22f6 --- /dev/null +++ b/pages/network/load_balancer/create_balancing/guide.en-ie.md @@ -0,0 +1,106 @@ +--- +title: Load balancing methods +excerpt: Discover the various load balancing algorithms available with the OVHcloud Load Balancer +updated: 2025-10-23 +--- + +## Objective + +The OVHcloud Load Balancer service supports a variety of load balancing algorithms for your services. This setting dictates how the Load Balancer distributes incoming client requests among the servers in a farm. + +**This guide introduces the various load balancing methods and explains how to modify them.** + +## Requirements + +- An [OVHcloud Load Balancer](/links/network/load-balancer) service in your OVHcloud account. +- Access to the [OVHcloud Control Panel](/links/manager). +- You need to have created a server farm. + +## Instructions + +### Available Load Balancing Algorithms + +The load balancing setting is applied at the server farm level and defines the method by which client requests are distributed among the servers within that farm. + +For an overview of the OVHcloud Load Balancer service components, please refer to the [Load Balancer Introduction](/pages/network/load_balancer/use_presentation) guide. + +|Algorithm|Features| +|---|---| +|**First**|Directs the connection to the first available server based on its ID (smallest to largest).| +|**LeastConn**|Selects the server with the lowest number of active connections. This is recommended for long-duration sessions with light traffic. The *RoundRobin* algorithm is used for tie-breaking among equally loaded servers.| +|**RoundRobin**|Distributes connections sequentially, one after the other, for each new request. **This is the default algorithm.**| +|**Source**|Uses a hash of the source IP address to consistently redirect the same client IP to the same server, provided the server remains operational.| +|**URI**|Uses a hash of part or all of the URI path to consistently redirect identical URIs to the same server, provided the server remains operational. *(Applicable to HTTP/HTTPS farms only.)*| + +### Modify a server farm’s load balancing method via the OVHcloud Control Panel + +- In the `Server farms`{.action} section (1), locate the desired farm. You can edit it by clicking the three dots on the right-hand side (2), then on `Change`{.action}. + +![Modify a farm](images/server_cluster_change.png){.thumbnail} + +In `Advanced settings`{.action}, modify the `Load balancing method`{.action}. + +![Modify a farm](images/distrib_mode_edit.png){.thumbnail} + +Once your preferred method is selected, click `Update`{.action}, then click `Apply configuration`{.action} in the yellow banner that appears. + +![Apply configuration](images/apply_config.png){.thumbnail} + +### Modify a server farm’s load balancing method via the OVHcloud API + +The load balancing method is changed by updating the corresponding field within the server farm configuration. + +#### View details on a server farm + +Use this api call to view the details of a server farm given its ID. In this example, we work with an HTTP farm: + +> [!api] +> +> @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/http/farm/{farmId} +> + +|Setting|Meaning| +|---|---| +|serviceName*|Your Load Balancer service ID| +|farmId*|The farm’s ID number| + +|Response (BackendHttp)|Meaning| +|---|---| +|farmId|The farm’s ID number| +|balance|The load balancing algorithm currently set for the farm| +|zone|Name of the zone in which the farm is configured| +|port|Port used to contact the servers configured on the farm| +|probe|Type of probe currently configured on the farm| +|displayName|Name given to this farm| +|stickiness|Connection monitoring method currently set for the farm| + +#### Modify a server farm’s load balancing method + +Use this api call to edit the settings of a server farm given its ID. In this example, we work with an HTTP farm. To modify the balancing method, update the `BackendHttp.balance` field with an available algorithm: + +> [!api] +> +> @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/http/farm/{id} +> + +|Setting|Meaning| +|---|---| +|serviceName*|Your Load Balancer service ID| +|farmId*|The farm’s ID number| +|BackendHttp.balance|Preferred balancing method for this farm| + +#### Apply the modifications + +> [!api] +> +> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh +> + +|Setting|Meaning| +|---|---| +|serviceName*|Your Load Balancer service ID| +|zone*|Name of the zone in which to deploy the configuration| + +## Go further + +Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/create_balancing/guide.en-us.md b/pages/network/load_balancer/create_balancing/guide.en-us.md new file mode 100644 index 00000000000..6236c3c22f6 --- /dev/null +++ b/pages/network/load_balancer/create_balancing/guide.en-us.md @@ -0,0 +1,106 @@ +--- +title: Load balancing methods +excerpt: Discover the various load balancing algorithms available with the OVHcloud Load Balancer +updated: 2025-10-23 +--- + +## Objective + +The OVHcloud Load Balancer service supports a variety of load balancing algorithms for your services. This setting dictates how the Load Balancer distributes incoming client requests among the servers in a farm. + +**This guide introduces the various load balancing methods and explains how to modify them.** + +## Requirements + +- An [OVHcloud Load Balancer](/links/network/load-balancer) service in your OVHcloud account. +- Access to the [OVHcloud Control Panel](/links/manager). +- You need to have created a server farm. + +## Instructions + +### Available Load Balancing Algorithms + +The load balancing setting is applied at the server farm level and defines the method by which client requests are distributed among the servers within that farm. + +For an overview of the OVHcloud Load Balancer service components, please refer to the [Load Balancer Introduction](/pages/network/load_balancer/use_presentation) guide. + +|Algorithm|Features| +|---|---| +|**First**|Directs the connection to the first available server based on its ID (smallest to largest).| +|**LeastConn**|Selects the server with the lowest number of active connections. This is recommended for long-duration sessions with light traffic. The *RoundRobin* algorithm is used for tie-breaking among equally loaded servers.| +|**RoundRobin**|Distributes connections sequentially, one after the other, for each new request. **This is the default algorithm.**| +|**Source**|Uses a hash of the source IP address to consistently redirect the same client IP to the same server, provided the server remains operational.| +|**URI**|Uses a hash of part or all of the URI path to consistently redirect identical URIs to the same server, provided the server remains operational. *(Applicable to HTTP/HTTPS farms only.)*| + +### Modify a server farm’s load balancing method via the OVHcloud Control Panel + +- In the `Server farms`{.action} section (1), locate the desired farm. You can edit it by clicking the three dots on the right-hand side (2), then on `Change`{.action}. + +![Modify a farm](images/server_cluster_change.png){.thumbnail} + +In `Advanced settings`{.action}, modify the `Load balancing method`{.action}. + +![Modify a farm](images/distrib_mode_edit.png){.thumbnail} + +Once your preferred method is selected, click `Update`{.action}, then click `Apply configuration`{.action} in the yellow banner that appears. + +![Apply configuration](images/apply_config.png){.thumbnail} + +### Modify a server farm’s load balancing method via the OVHcloud API + +The load balancing method is changed by updating the corresponding field within the server farm configuration. + +#### View details on a server farm + +Use this api call to view the details of a server farm given its ID. In this example, we work with an HTTP farm: + +> [!api] +> +> @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/http/farm/{farmId} +> + +|Setting|Meaning| +|---|---| +|serviceName*|Your Load Balancer service ID| +|farmId*|The farm’s ID number| + +|Response (BackendHttp)|Meaning| +|---|---| +|farmId|The farm’s ID number| +|balance|The load balancing algorithm currently set for the farm| +|zone|Name of the zone in which the farm is configured| +|port|Port used to contact the servers configured on the farm| +|probe|Type of probe currently configured on the farm| +|displayName|Name given to this farm| +|stickiness|Connection monitoring method currently set for the farm| + +#### Modify a server farm’s load balancing method + +Use this api call to edit the settings of a server farm given its ID. In this example, we work with an HTTP farm. To modify the balancing method, update the `BackendHttp.balance` field with an available algorithm: + +> [!api] +> +> @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/http/farm/{id} +> + +|Setting|Meaning| +|---|---| +|serviceName*|Your Load Balancer service ID| +|farmId*|The farm’s ID number| +|BackendHttp.balance|Preferred balancing method for this farm| + +#### Apply the modifications + +> [!api] +> +> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh +> + +|Setting|Meaning| +|---|---| +|serviceName*|Your Load Balancer service ID| +|zone*|Name of the zone in which to deploy the configuration| + +## Go further + +Join our [community of users](/links/community). \ No newline at end of file From dca78c2bf3341bf94d6bb96f3473718a18a32952 Mon Sep 17 00:00:00 2001 From: Yoann Cosse Date: Fri, 24 Oct 2025 17:37:10 +0200 Subject: [PATCH 21/23] Duplication + Date update + Translations deletion --- llm-config/config.json | 34 +++ llm-config/system-prompts/generation.md | 70 ++++++ llm-config/system-prompts/guide-refinement.md | 30 +++ llm-config/system-prompts/guide-to-prompt.md | 109 +++++++++ llm-config/system-prompts/translation.md | 63 +++++ llm-config/terminology/translations.csv | 215 ++++++++++++++++++ .../case_blue_green/guide.en-asia.md | 2 +- .../case_blue_green/guide.en-au.md | 2 +- .../case_blue_green/guide.en-ca.md | 2 +- .../case_blue_green/guide.en-gb.md | 2 +- .../case_blue_green/guide.en-sg.md | 2 +- .../case_blue_green/guide.en-us.md | 2 +- .../case_blue_green/guide.fr-ca.md | 8 +- .../case_blue_green/guide.fr-fr.md | 8 +- .../load_balancer/case_smtp/guide.en-asia.md | 111 +++++---- .../load_balancer/case_smtp/guide.en-ca.md | 111 +++++---- .../load_balancer/case_smtp/guide.en-gb.md | 2 +- .../load_balancer/case_smtp/guide.en-sg.md | 111 +++++---- .../load_balancer/case_smtp/guide.en-us.md | 111 +++++---- .../load_balancer/case_smtp/guide.fr-ca.md | 158 ++++++------- .../load_balancer/case_smtp/guide.fr-fr.md | 2 +- .../create_balancing/guide.de-de.md | 105 --------- .../create_balancing/guide.en-asia.md | 2 +- .../create_balancing/guide.en-au.md | 2 +- .../create_balancing/guide.en-ca.md | 2 +- .../create_balancing/guide.en-gb.md | 2 +- .../create_balancing/guide.en-ie.md | 2 +- .../create_balancing/guide.en-sg.md | 2 +- .../create_balancing/guide.en-us.md | 2 +- .../create_balancing/guide.es-es.md | 107 --------- .../create_balancing/guide.es-us.md | 107 --------- .../create_balancing/guide.fr-ca.md | 2 +- .../create_balancing/guide.fr-fr.md | 2 +- .../create_balancing/guide.it-it.md | 105 --------- .../create_balancing/guide.pl-pl.md | 106 --------- .../create_balancing/guide.pt-pt.md | 105 --------- .../order_freecertificate/guide.en-asia.md | 2 +- .../order_freecertificate/guide.en-au.md | 2 +- .../order_freecertificate/guide.en-ca.md | 2 +- .../order_freecertificate/guide.en-gb.md | 2 +- .../order_freecertificate/guide.en-sg.md | 2 +- .../order_freecertificate/guide.en-us.md | 2 +- .../order_freecertificate/guide.fr-ca.md | 2 +- .../order_freecertificate/guide.fr-fr.md | 2 +- 44 files changed, 852 insertions(+), 972 deletions(-) create mode 100644 llm-config/config.json create mode 100644 llm-config/system-prompts/generation.md create mode 100644 llm-config/system-prompts/guide-refinement.md create mode 100644 llm-config/system-prompts/guide-to-prompt.md create mode 100644 llm-config/system-prompts/translation.md create mode 100644 llm-config/terminology/translations.csv delete mode 100644 pages/network/load_balancer/create_balancing/guide.de-de.md delete mode 100644 pages/network/load_balancer/create_balancing/guide.es-es.md delete mode 100644 pages/network/load_balancer/create_balancing/guide.es-us.md delete mode 100644 pages/network/load_balancer/create_balancing/guide.it-it.md delete mode 100644 pages/network/load_balancer/create_balancing/guide.pl-pl.md delete mode 100644 pages/network/load_balancer/create_balancing/guide.pt-pt.md diff --git a/llm-config/config.json b/llm-config/config.json new file mode 100644 index 00000000000..85442280015 --- /dev/null +++ b/llm-config/config.json @@ -0,0 +1,34 @@ +{ + "runMidscene": { + "model": "Qwen2.5-VL-72B-Instruct", + "configuration": { + "baseURL": "https://oai.endpoints.preprod.ai.cloud.ovh.net/v1", + "cache": "1" + } + }, + "translateGuide": { + "model": "Qwen3-32B", + "configuration": { + "baseURL": "https://oai.endpoints.preprod.ai.cloud.ovh.net/v1" + }, + "maxTokens": 4000, + "temperature": 0.2 + }, + "generateGuide": { + "model": "Meta-Llama-3_3-70B-Instruct", + "configuration": { + "baseURL": "https://oai.endpoints.preprod.ai.cloud.ovh.net/v1" + }, + "maxTokens": 5000, + "temperature": 0.2, + "topP": 1 + }, + "guideToPrompt": { + "model": "Meta-Llama-3_3-70B-Instruct", + "configuration": { + "baseURL": "https://oai.endpoints.preprod.ai.cloud.ovh.net/v1" + }, + "maxTokens": 5000, + "temperature": 0.2 + } +} diff --git a/llm-config/system-prompts/generation.md b/llm-config/system-prompts/generation.md new file mode 100644 index 00000000000..a6a502ad84d --- /dev/null +++ b/llm-config/system-prompts/generation.md @@ -0,0 +1,70 @@ +**Technical Writing Task** + +Act as a technical writer to create a comprehensive guide based on the provided steps. Ensure that the text is logical, clear, and concise, making it easily understandable for both technical and non-technical readers. + +**Guide Requirements** + +- Write the guide in the specified language: {{locale}} +- Improve the text in terms of clarity, quality, and readability +- Use footnotes to explain technical terms related to the computer domain +- Adhere to industry standards for technical documentation +- Ensure the guide is concise and easy to follow + +**Guide Details** + +- Guide name: {{scenario}} +- Base URL: {{base_url}} (to be mentioned in the first step) +- add balise before first step + +**Steps** + +Here is the list of steps the playwright AI agent follows +in order to perform the actions explained in the guide: + +```yaml +{{steps}} +``` + +Note that each step provided should not necessarily be +a step of the guide. + +For `screenshot` steps, do not write any text, +instead generate a markdown image using path, filename +and, if provided, description, right after the last previous step. + +Example format: + +```markdown + +![Descriptive alt text inspired by description or filename](path/filename) + +``` + +**Additional Requirements** + +- No need to number steps, just give them a title +- Provide additional information and context in each step to enhance clarity +- Include a header and footer with relevant information +- Use Markdown format for the guide +- Do not add scrolling steps +- Skip a line between each steps + {{custom_instructions}} + +**Document Header** + +Each document should begin with the following header: + +```markdown +--- +title: "Add a meaningful title here (generated by AI)" +excerpt: "Add a meta description of the guide" +updated: {{date}} +flag: hidden +--- +``` + +**Output Format** + +The output must be in valid Markdown format, do not encapsulate the result in a fenced code block. + +Please create the guide based on the provided steps, following the requirements and guidelines above. diff --git a/llm-config/system-prompts/guide-refinement.md b/llm-config/system-prompts/guide-refinement.md new file mode 100644 index 00000000000..86f22819088 --- /dev/null +++ b/llm-config/system-prompts/guide-refinement.md @@ -0,0 +1,30 @@ +**Guide Refinement Task** + +Act as a technical editor to polish the provided guide. Make minimal but impactful improvements to enhance readability while preserving the original structure and content. + +**Input** + +```markdown +{{guide}} +``` + +**Your Task** + +Review the guide and make light edits to: + +- Remove any obviously redundant or unnecessary sentences +- Simplify overly complex phrasing while keeping technical accuracy +- Ensure the tone feels natural and professional (not robotic) +- Fix any grammatical or stylistic issues + +**Important Constraints** + +- Keep all steps and their titles intact unless truly redundant +- Preserve all technical details, footnotes, and formatting +- Maintain the document header and structure +- Do not reorganize or heavily rewrite content +- Make only essential improvements + +**Output Format** + +Provide the refined guide in valid Markdown format. Do not encapsulate the result in a fenced code block. diff --git a/llm-config/system-prompts/guide-to-prompt.md b/llm-config/system-prompts/guide-to-prompt.md new file mode 100644 index 00000000000..e13cffd43d7 --- /dev/null +++ b/llm-config/system-prompts/guide-to-prompt.md @@ -0,0 +1,109 @@ +**Task: Convert User Guide into Bot Actions** + +Your goal is to break down a given user guide into a series of steps that a browser-manipulating bot can follow. Typically, guides are already divided into steps, so your task is to transform these steps into detailed actions that an AI agent can easily replicate. +Note that you will be already logged in when accessing OVHcloud manager, so you don't need to add steps concerning authentification. +Links described as "/link/manager" corresponds to "https://www.ovh.com/manager/#/" +Note that your name as a user will be "POC Guides". + +**Requirements:** + +1. Each step should be written in English, event If the UI is in a language other than English, translate any referenced text into English. +2. Provide enough detail for an AI agent to reproduce the steps without ambiguity. +3. When a value needs to be filled, it should be valid. +4. Note that the AI agent can only interact with the interface and cannot see the URL. + +**Input:** + +The user guide to be converted is provided below: + +```md +{{guide}} +``` + +**Output Format:** + +The output should be in the following format: + +```json +{ + "target": { + "url": "https://website.com/exact-path", + "viewportWidth": 1280, + "viewportHeight": 720 + }, + "tasks": [ + { + "name": "Task Name", + "flow": [ + { + "type": "aiWaitFor", + "action": "Perform action 1" + }, + { + "type": "ai", + "action": "Perform action 2" + } + ] + } + ] +} +``` + +**Example:** + +For reference, here is an example of what the output might look like: + +```json +{ + "target": { + "url": "https://url-of-the-starting-point", + "viewportWidth": 1280, + "viewportHeight": 720 + }, + "tasks": [ + { + "name": "How to change date of birth", + "flow": [ + { + "type": "aiWaitFor", + "action": "You are on the page 'My Account'" + }, + { + "type": "ai", + "action": "Click on 'My informations'" + }, + { + "type": "aiWaitFor", + "action": "Wait for the page to finish loading" + }, + { + "type": "ai", + "action": "Click on Edit" + }, + { + "type": "aiAssert", + "action": "The user information form should be visible" + }, + { + "type": "ai", + "action": "Click the 'Date of birth' or 'Birthday' field" + }, + { + "type": "ai", + "action": "Update the field with a random date" + }, + { + "type": "ai", + "action": "Click on confirm" + }, + { + "type": "aiWaitFor", + "action": "A confirmation text should appear" + } + ] + } + ] +} +``` + +Please convert the provided user guide into this format, following the requirements and guidelines above. diff --git a/llm-config/system-prompts/translation.md b/llm-config/system-prompts/translation.md new file mode 100644 index 00000000000..0d5cd2d7ccf --- /dev/null +++ b/llm-config/system-prompts/translation.md @@ -0,0 +1,63 @@ +/set nothink + +You are a translation tool. Your purpose is to create an accurately translated output text from a guide markdown. + +Follow these steps: + +1. The source language is {{source_lang}}. +2. Proceed with the translation of the user input text into {{target_lang}}. Strictly follow the formatting instructions specified below. +3. Output ONLY the completed translated text without any additional commentary, explanations, or formatting markers. Just pure markdown and do not encapsulate response in code block. + +## Tone & Style + +The input text is of a technical nature, specifically: + +- How to use OVHcloud products (user instructions, FAQ, tutorial) + Do not alter the tone or style. Your goal is to provide an accurate translation of the input text. + +## Formatting instructions + +- The input text is formatted in Markdown. Leave all Markdown formatting intact. +- The input text might contain HTML tags. Leave all HTML tags exactly as they are. (example: ). +- The input text includes custom Markdown formats. Leave all Markdown formats and their markers intact. Here are examples: + - Page frontmatter + - Relative links to internal pages + - Relative links to images + - External links + - Triple forward slashes (usage example: /// details | ///) + - Custom Markdown formats identfied by: [!api], [!primary], [!warning], [!alert], [!success], [!tabs] + - Button labels, example: `Button label`{.action} + - Labels, example: `Label` +- The input text may contain french quotation marks: « ». Rewrite them into English quotation marks: "". + +## Translation exceptions + +- Preserve the content of code blocks (English). +- Do not translate HTML link fragments and anchors. +- The structure of the input text may often contain certain sections names which must have standardized translations. Refer to the "CSV-formatted list of sections" for the approved translations of these sections. Ensure that you use these exact translations consistently throughout the guide, without introducing any variations. +- Some terms are fixed for each target language. Use the "CSV-formatted listof fixed terminology" below as reference for the proper translated versions. Do not translate these terms differently. + +### CSV-formatted list of sections + +```csv +French;English;German;Spanish;Italian;Polish;Portuguese +Objectif;Objective;Ziel;Objetivo;Obiettivo;Wprowadzenie;Objetivo +Prérequis;Requirements;Voraussetzungen;Requisitos;Prerequisiti;Wymagania początkowe;Requisitos +En pratique;Instructions;In der praktischen Anwendung;Procedimiento;Procedura;W praktyce;Instruções +Aller plus loin;Go further;Weiterführende Informationen;Más información;Per saperne di più;Sprawdź również;Quer saber mais? +Échangez avec notre [communauté d'utilisateurs](/links/community).;Join our [community of users](/links/community).;Treten Sie unserer [User Community](/links/community) bei.;Interactúe con nuestra [comunidad de usuarios](/links/community).;Contatta la nostra [Community di utenti](/links/community).;Dołącz do [grona naszych użytkowników](/links/community).;Fale com a nossa [comunidade de utilizadores](/links/community). +``` + +### CSV-formatted list of fixed terminology + +```csv +{{terminology_translations}} +``` + +## Text to translate + +**CRITICAL: Output the translated content directly as raw markdown. Do NOT wrap your response in code blocks (```), do NOT add explanatory text before or after, and do NOT include phrases like "Here is the translation" or similar commentary. Also, do not try to fix the markdown in any way** + +```markdown +{{guide}} +``` diff --git a/llm-config/terminology/translations.csv b/llm-config/terminology/translations.csv new file mode 100644 index 00000000000..b4516bbdfba --- /dev/null +++ b/llm-config/terminology/translations.csv @@ -0,0 +1,215 @@ +German;English;Spanish;French;Italian;Polish;Portuguese +OVHcloud Kundencenter;OVHcloud Control Panel;área de cliente de OVHcloud;espace client OVHcloud;Spazio Cliente OVHcloud;Panel klienta OVHcloud;área de cliente OVHcloud +Zerto;Zerto;Zerto;Zerto;Zerto;Zerto;Zerto +Nutanix on OVHcloud;Nutanix on OVHcloud;Nutanix on OVHcloud;Nutanix on OVHcloud;Nutanix on OVHcloud;Nutanix on OVHcloud;Nutanix on OVHcloud +Performance 4;Performance 4;Performance 4;Performance 4;Performance 4;Performance 4;Perf 4 +Analytics Manager;Analytics Manager;Analytics Manager;Analytics Manager;Analytics Manager;Analytics Manager;Analytics Manager +Quota- und Regionmanagement;Quota and Region Management;Quota and Region Management;Quota and region management;Quota and Region Management;Quota and Region Management;Quota and Region Management +Boost;Boost;Boost;Boost;Boost;Boost;Boost +CDN;CDN;CDN;CDN;CDN;CDN;CDN +;water cooling;;watercooling;;; +Private Exchange;Private Exchange;Private Exchange;Private Exchange;Private Exchange;Private Exchange;Private Exchange +;retrieval-augmented generation;;génération augmentée par récupération;;; +;Special Terms and Conditions;;Conditions Particulières;;; +Classic Block Storage;Classic Block Storage;Classic;Classic Block Storage;Classic;Classic Block Storage;Classic Block Storage +Kafka;Kafka;Kafka;Kafka;Kafka;Kafka;Kafka +SAP HANA on Private Cloud;SAP HANA on Private Cloud;SAP HANA on Private Cloud;SAP HANA on Private Cloud;SAP HANA on Private Cloud;SAP HANA on Private Cloud;SAP HANA on Private Cloud +GPU;GPU;GPU;GPU;GPU;GPU;GPU +Cloud Disk Array;Cloud Disk Array;Cloud Disk Array;Cloud Disk Array;Cloud Disk Array;Cloud Disk Array;Cloud Disk Array +Elite;Elite;Elite;Elite;Elite;Elite;Elite +;;;Availability Zone;;Availability Zone; +Environmental Impact Tracker;Environmental Impact Tracker;Environmental Impact Tracker;Environmental Impact Tracker;Environmental Impact Tracker;Environmental Impact Tracker;Environmental Impact Tracker +OVHcloud Partner Program;OVHcloud Partner Program;OVHcloud Partner Program;OVHcloud Partner program;OVHcloud Partner Program;OVHcloud Partner Program;OVHcloud Partner program +;;;Réseau et sécurité;;Sieć i bezpieczeństwo; +;Email solutions;Soluciones de correo;Solutions e-mail;Soluzioni email;Rozwiązania poczty elektronicznej;Soluções de e-mail +Standard Support;Standard Support;Soporte Standard;Support Standard;Supporto Standard;Standard;Suporte Standard +Veeam Managed Backup;Veeam Managed Backup;Veeam Managed Backup;Veeam Managed Backup;Veeam Managed Backup;Veeam Backup Managed;Veeam Managed Backup +MySQL;MySQL;MySQL;MySQL;MySQL;MySQL;MySQL +High Speed Block Storage;High Speed Block Storage;High Speed;High Speed Block Storage;High Speed;High Speed Block Storage;High Speed Block Storage +OVHcloud Load Balancer;OVHcloud Load Balancer;Load Balancer de OVHcloud;OVHcloud Load Balancer;Load Balancer OVHcloud;OVHcloud Load Balancer;Load Balancer da OVHcloud +;;;Environmental Impact Tracker;;Environmental Impact Tracker; +Trusted Exchange;Trusted Exchange;Trusted Exchange;Trusted Exchange;Trusted Exchange;Trusted Exchange;Trusted Exchange +;Collaborative solutions;Soluciones colaborativas;Solutions collaboratives;Soluzioni collaborative;Rozwiązania do pracy zespołowej;Soluções colaborativas +Data Processing Engine;Data Processing Engine;Data Processing Engine;Data Processing Engine;Data Processing Engine;Data Processing Engine;Data Processing Engine +Kafka Connect;Kafka Connect;Kafka Connect;Kafka Connect;Kafka Connect;Kafka Connect;Kafka Connect +On-Prem Cloud Platform;On-Prem Cloud Platform;On-Prem Cloud Platform;On-Prem Cloud Platform;On-Prem Cloud Platform;On-Prem Cloud Platform;On-Prem Cloud Platform +Advanced Collaborative Suite;Advanced collaborative suite;Suite colaborativa Advanced;Suite collaborative Advanced;Suite collaborativa Advance;Advanced collaborative suite;Suite colaborativa Advanced +Cloud Web 1;Cloud Web 1;Cloud Web 1;Cloud Web 1;Cloud Web 1;Cloud Web 1;Cloud Web 1 +Local Zones;Local Zones;Local Zones;Local Zones;Local Zones;Local Zones;Local Zones +Volume Snapshot;Volume Snapshot;Volume Snapshot;Volume Snapshot;Volume Snapshot;Volume Snapshot;Volume Snapshot +CDN Security;CDN Security;CDN Security;CDN Security;CDN Security;CDN Security;CDN Security +CDN Advanced;CDN Advanced;CDN Advanced;CDN Advanced;CDN Advanced;CDN Advanced;CDN Advanced +Bring your own IP (BYOIP);Bring Your Own IP (BYOIP);Bring Your Own IP (BYOIP);Bring Your Own IP (BYOIP);Bring Your Own IP (BYOIP);Bring your own IP (BYOIP);Bring your own IP (BYOIP) +;business-critical information;;informations stratégique;;; +Hosted Private Cloud powered by Anthos;Hosted Private Cloud powered by Anthos;Hosted Private Cloud powered by Anthos;Hosted Private Cloud powered by Anthos;Hosted Private Cloud powered by Anthos;Hosted Private Cloud powered by Anthos;Hosted Private Cloud powered by Anthos +Backup;Backup;Backup;Backup;Backup;Backup;Backup +E-Mail Pro;Email Pro;Email Pro;E-mail Pro;Email Pro;E-mail Pro;E-mail Pro +Managed Big Data Cluster;Managed Big Data Cluster;Managed Big Data Cluster;Managed Big Data Cluster;Managed Big Data Cluster;Managed Big Data Cluster;Managed Big Data Cluster +Managed Private Registry;Managed Private Registry;Managed Private Registry;Managed Private Registry;Managed Private Registry;Managed Private Registry;Managed Private Registry +;Web Hosting;Hosting;Hébergements web;Hosting Web;Hosting;Alojamentos web +Scale;Scale;Scale;Scale;Scale;Scale;Scale +CDN Basic;CDN Basic;CDN Basic;CDN Basic;CDN Basic;CDN Basic;CDN Basic +;Network Services;Servicios de red;Services réseau;Servizi di rete;Usługi sieciowe;Serviços de rede +;Levels of support;Niveles de soporte;Niveaux de support;Livelli di supporto;Poziomy wsparcia;Níveis de suporte +Cold Archive;Cold Archive;Cold Archive;Cold Archive;Cold Archive;Cold Archive;Cold Archive +Object Storage;Object Storage;Object Storage;Object storage;Object Storage;Object Storage;Object Storage +Starter;Starter;Starter;Starter;Starter;Starter;Starter +;;;Offre packagée;;Oferta pakietowa; +Das private Netzwerk vRack;vRack private network;Red privada vRack;Réseau privé vRack;Rete privata vRack;Prywatna sieć vRack;Rede privada vRack +;compute resources;;ressources de calcul;;; +Start 10M;Start 10M;Start 10M;Start 10M;Start 10M;Start 10M;Start 10M +Performance Hosting;Performance Hosting;Hosting Performance;Hébergement Performance;Hosting Performance;Hosting Performance;Alojamento Performance +Cloud Webhosting;Cloud Web Hosting;Hosting Cloud Web;Hébergement Cloud Web;Hosting Cloud Web;Hosting Cloud Web;Alojamento Cloud Web +Control Center;Control Center;Control Center;Control Center;Control Center;Control Center;Control Center +Hosted Exchange;Hosted Exchange;Hosted Exchange;Hosted Exchange;Hosted Exchange;Hosted Exchange;Hosted Exchange +High Grade;High Grade;High Grade;High Grade;High Grade;High Grade;High Grade +Data Catalog;Data Catalog;Data Catalog;Data Catalog;Data Catalog;Data Catalog;Data Catalog +;;;Bare Metal Cloud;;Bare Metal Cloud; +IOPS;IOPS;IOPS;IOPS;IOPS;IOPS;IOPS +VPS;VPS;VPS;VPS;VPS;VPS;VPS +Additional IP;Additional IP;Additional IP;Additional IP;Additional IP;Additional IP;Additional IP +;Domain Name Registrant;;Titulaire d’un Nom de Domaine;;; +HYCU for ovhcloud;HYCU for ovhcloud;HYCU for ovhcloud;HYCU for ovhcloud;HYCU for ovhcloud;;HYCU for ovhcloud +OpenSearch;OpenSearch;OpenSearch;OpenSearch;OpenSearch;OpenSearch;OpenSearch +Trusted Zone;Trusted Zone;Trusted Zone;Zone de confiance;Trusted Zone;Trusted Zone;Zonas de Confiança +Enterprise File Storage;Enterprise File Storage;Enterprise File Storage;Enterprise File Storage;Enterprise File Storage;Enterprise File Storage;Enterprise File Storage +Private Image Catalog;Private Image Catalog;Private Image Catalog;Private Image catalog;Private Image Catalog;Private Image Catalog;Private Image Catalog +Managed Kubernetes Service;Managed Kubernetes Service;Managed Kubernetes Service;Managed Kubernetes Service;Managed Kubernetes;Managed Kubernetes;Managed Kubernetes Service +;Domain names;Dominios;Noms de domaine;Domini;Domeny;Nomes de domínio +SSL-Zertifikat "Sectigo DV";Sectigo DV SSL certificate;Certificado SSL Sectigo DV;Certificat SSL Sectigo DV;Certificato SSL Sectigo DV;Certyfikat SSL Sectigo DV;Certificado SSL Sectigo DV +;Web security;Protección web;Sécurité web;Sicurezza Web;Bezpieczeństwo sieci;Segurança web +;Guaranteed resources;Guaranteed Resources;Guaranteed resources;Guaranteed Resources;Guaranteed Resources;Guaranteed Resources +;;;PERFORMANCE 4;;Performance 4; +Public VCF as-a-Service;Public VCF as-a-Service;Public VCF as-a-Service;Public VCF as-a-Service;Public VCF as-a-Service;Public VCF as-a-Service;Public VCF as-a-Service +Game;Game;Game;Game;Game;Game;Game +OVHcloud Link Aggregation (OLA);OVHcloud Link Aggregation (OLA);OVHcloud Link Aggregation (OLA);OVHcloud Link Aggregation (OLA);OVHcloud Link Aggregation (OLA);OVHcloud Link Aggregation (OLA);OVHcloud Link Aggregation (OLA) +SharePoint;SharePoint;SharePoint;SharePoint;SharePoint;SharePoint;SharePoint +Enterprise Support;Enterprise Support;Soporte Enterprise;Support Enterprise;Supporto Enterprise;Enterprise;Suporte Enterprise +Rise;Rise;Rise;Rise;Rise;Rise;Rise +CDN Security;CDN Security;CDN Security;CDN Security;CDN Security;CDN Security;CDN Security +Lakehouse Manager;Lakehouse Manager;Lakehouse Manager;Lakehouse Manager;Lakehouse Manager;Lakehouse Manager;Lakehouse Manager +;conformance program;;programme de conformité;;; +Business Support;Business Support;Soporte Business;Support Business;Supporto Business;Business;Suporte Business +;Options;Opciones;Options;Opzioni;Opcje;Opções +;;;Sécurité web;;Bezpieczeństwo sieci; +OVHcloud AI Training;OVHcloud AI Training;OVHcloud AI Training;OVHcloud AI Training;OVHcloud AI Training;OVHcloud AI Training;OVHcloud AI Training +;Affiliates;;Sociétés Apparentées;;; +File Storage;File Storage;File storage;File storage;File Storage;File storage;File storage +Local Zone;Local Zone;Local Zone;Local Zone;Local Zone;Local Zone;Local Zone +Managed Veeam for VCD;Managed Veeam for VCD;Managed Veeam for VCD;Managed Veeam for VCD;Managed Veeam for VCD;Managed Veeam for VCD;Managed Veeam for VCD +Enterprise Cloud Databases;Enterprise Cloud Databases;Enterprise Cloud Databases;Enterprise Cloud Databases;Enterprise Cloud Databases;Enterprise Cloud Databases;Enterprise Cloud Databases +Logs Data Platform;Logs Data Platform;Logs Data Platform;Logs Data Platform;Logs Data Platform;Logs Data Platform;Logs Data Platform +Performance 1;Performance 1;Performance 1;Performance 1;Performance 1;Performance 1;Perf 1 +DDoS-Schutz-Infrastruktur;Anti-DDoS infrastructure;Infraestructura anti-DDoS;Infrastructure Anti-DDoS;Infrastruttura anti-DDoS;Infrastruktura Anty-DDoS;Infraestrutura Anti-DDoS +MongoDB;MongoDB;MongoDB;MongoDB;MongoDB;MongoDB;MongoDB +NVIDIA NGC Platform;NVIDIA NGC Platform;NVIDIA NGC Platform;NVIDIA NGC Platform;NVIDIA NGC Platform;NVIDIA NGC Platform;NVIDIA NGC Platform +So you Start;So you Start;So you Start;So you Start;So you Start;So you Start;So you Start +Data Processing;Data Processing;Data Processing;Data Processing;Data Processing;Data Processing;Data Processing +Applications Services;Applications Services;Applications Services;Applications Services;Applications Services;Applications Services;Applications Services +;Dedicated Servers;Servidores dedicados;Serveurs dédiés;Server dedicati;Serwery dedykowane;Servidores dedicados +Cassandra;Cassandra;Cassandra;Cassandra;Cassandra;Cassandra;Cassandra +Basic Hosting;Personal Hosting;Hosting Personal;Hébergement Perso;Hosting Personale;Hosting Perso;Alojamento Perso +;;;Sécurité des hôtes et services;;Bezpieczeństwo hostów i usług; +Archive;Archive;Archive;Archive;Archive;Archive;Archive +;;;PERFORMANCE 3;;Performance 3; +M3DB;M3DB;M3DB;M3DB;M3DB;M3DB;M3DB +;Public bandwidth;Ancho de banda público;Bande passante publique;Banda passante pubblica;Przepustowość do sieci publicznej;Largura de banda pública +SSL;SSL;SSL;SSL;SSL;SSL;SSL +Redis;Redis;Redis;Redis;Redis;Redis;Redis +Grafana;Grafana;Grafana;Grafana;Grafana;Grafana;Grafana +Performance 3;Performance 3;Performance 3;Performance 3;Performance 3;Performance 3;Perf 3 +PostgreSQL;PostgreSQL;PostgreSQL;PostgreSQL;PostgreSQL;PostgreSQL;PostgreSQL +Comfort;Comfort;Comfort;Comfort;Comfort;Comfort;Comfort +;;;Hosted Private Cloud powered by VMware;;Hosted Private Cloud powered by VMware; +AI Notebooks;AI Notebooks;AI Notebooks;AI Notebooks;AI Notebooks;AI Notebooks;AI Notebooks +Value;Value;Value;Value;Value;Value;Value +Instance Backup;Instance Backup;Instance Backup;Instance Backup;Instance Backup;Instance Backup;Instance Backup +;Project Management;Project Management;Project management;Project Management;Project Management;Project Management +;white area;;Zone blanche;;; +Marketplace;Marketplace;Marketplace;Marketplace;Marketplace;Marketplace;Marketplace +;Infrastructure protection;Protección de infraestructura;Protection de l'infrastructure;Protezione dell'infrastruttura;Ochrona infrastruktury;Proteção da infraestrutura +Public Image Catalog;Public Image Catalog;Public Image Catalog;Public Image catalog;Public Image Catalog;Public Image Catalog;Public Image Catalog +;;;Pack Nutanix Advanced;;Pakiet Nutanix Advanced; +;SSL certificate as-a-Service;Certificado SSL as a Service;Certificat SSL as a Service;SSL Certificate as a Service;Certyfikat SSL as a Service;Certificado SSL as a Service +;;;PERFORMANCE 2;;Performance 2; +Standard Object Storage;Standard Object Storage;Standard Object Storage;Standard Object Storage;Standard Object Storage;Standard Object Storage;Standard Object Storage +;Web Hosting options;Opciones de alojamiento web;Options hébergement web;Opzioni hosting Web;Opcje hostingu;Opções de alojamento web +;AI & Machine Learning;AI & Machine Learning;AI & machine learning;AI & Machine Learning;AI & Machine Learning;AI & Machine Learning +Trusted Zone;Trusted Zone;Trusted Zone;Zone de confiance;Trusted Zone;Trusted Zone;Zonas de Confiança +Offsite Replication;Offsite Replication;Offsite Replication;Offsite Replication;Offsite Replication;Offsite Replication;Offsite Replication +Open Trusted Cloud;Open Trusted Cloud;Open Trusted Cloud;Open Trusted Cloud;Open Trusted Cloud;Open Trusted Cloud;Open Trusted Cloud +;;;Visibilité Pro;;Widoczna firma; +Discovery;Discovery;Discovery;Discovery;Discovery;Discovery;Discovery +Advance;Advance;Advance;Advance;Advance;Advance;Advance +DNSSEC;DNSSEC;DNSSEC;DNSSEC;DNSSEC;DNSSEC;DNSSEC +DDoS-Schutz;DDoS protection;DDoS Protection;Protection Anti-DDoS;Protezione anti-DDoS;Ochrona Anty-DDoS;Proteção DDoS +CDN Infrastructure;CDN Infrastructure;CDN Infrastructure;CDN Infrastructure;CDN Infrastructure;CDN Infrastructure;CDN Infrastructure +Metal Instance;Metal Instance;Metal Instance;Metal Instance;Metal Instance;Metal Instance;Metal Instance +Sicherheit von Hosts und Diensten (Hosted Private Cloud);Security for hosts and services (Hosted Private Cloud);Protección de hosts y servicios solo para Hosted Private Cloud;Sécurité des hôtes et services (Hosted Private Cloud);Sicurezza di host e servizi (Hosted Private Cloud);Bezpieczeństwo hostów i usług (Hosted Private Cloud);Segurança dos hosts e serviços (Hosted Private Cloud) +ML Serving;ML Serving;ML Serving;ML Serving;ML Serving;ML Serving;ML Serving +Data Platform;ForePaaS;Data Platform;Data Platform;Data Platform;Data Platform;Data Platform +;SMS;SMS;SMS;SMS;Usługa SMS; +Kimsufi;Kimsufi;Kimsufi;Kimsufi;Kimsufi;Kimsufi;Kimsufi +;Security for hosts and services;Protección de hosts y servicios;Sécurité des hôtes et services;Sicurezza di host e servizi;;Segurança dos hosts e serviços +Start SQL-Datenbanken;Start SQL Databases;Bases de datos Start SQL;Bases de données Start SQL;Database Start SQL;Bazy danych Start SQL;Bases de dados Start SQL +;Edge;;périphérie;;; +SSL-Zertifikat "Let's Encrypt";Let's Encrypt SSL certificate;Certificado SSL Let's Encrypt;Certificat SSL Let's Encrypt;Certificato SSL Let's Encrypt;Certyfikat SSL Let's Encrypt;Certificado SSL Let's Encrypt +Plesk Hosting (EOL);Plesk Hosting (EOL);Hosting Plesk (EOL);Hébergement Plesk (EOL);Hosting Plesk (EOL);Hosting Plesk (EOL);Alojamento Plesk (EOL) +Console Connect;Console Connect;Console Connect;Console Connect;Console Connect;Console Connect;Console Connect +Performance 2;Performance 2;Performance 2;Performance 2;Performance 2;Performance 2;Perf 2 +Microsoft 365;Microsoft 365;Microsoft 365;Microsoft 365;Microsoft 365;Microsoft 365;Microsoft 365 +;;;computer vision;;widzenie komputerowe; +;vRack Services;;;;vRack Services; +;;;Services et certifications;;Usługi i certyfikaty; +Kafka MirrorMaker;Kafka MirrorMaker;Kafka MirrorMaker;Kafka MirrorMaker;Kafka MirrorMaker;Kafka MirrorMaker;Kafka MirrorMaker +;;;Pack Nutanix Standard;;Pakiet Nutanix Standard; +OVHcloud Connect;OVHcloud Connect;OVHcloud Connect;OVHcloud Connect;OVHcloud Connect;OVHcloud Connect;OVHcloud Connect +Pro Hosting;Professional Hosting;Hosting Profesional;Hébergement Pro;Hosting Pro;Hosting Pro;Alojamento Pro +Storage;Storage;Storage;Storage;Storage;Storage;Storage +;Security;Seguridad;Sécurité;Sicurezza;Bezpieczeństwo;Segurança +Cloud Archive;Cloud Archive;Cloud Archive;Cloud Archive;Cloud Archive;Cloud Archive;Cloud Archive +SecNumCloud;SecNumCloud;SecNumCloud;SecNumCloud;SecNumCloud;SecNumCloud;SecNumCloud +;Data Analytics;Data Analytics;Data Analytics;Data Analytics;Data Analytics;Data Analytics +;;;Stockage et sauvegarde;;Przechowywanie i kopie zapasowe; +;decoupling;;découplage;;; +;Data localisation;;Localisation des données;;; +Eco Dedicated Server;Eco Dedicated Servers;Servidores dedicados Eco;Serveurs dédiés Eco;Server dedicati Eco;Serwery dedykowane Eco;Servidores dedicados Eco +Managed Rancher Service;Managed Rancher Service;Managed Rancher Service;Managed Rancher Service;Managed Rancher Service;Managed Rancher Service;Managed Rancher Service +;;;Offre Nutanix on OVHcloud packagée;;Oferta pakietowa Nutanix on OVHcloud; +High Performance Object Storage;High Performance Object Storage;High Performance Object Storage;High Performance Object Storage;High Performance Object Storage;High Performance Object Storage;High Performance Object Storage +;Service Endpoint;;;;Service Endpoint; +Bare Metal Cloud Netzwerkdienste;Network Services for Bare Metal Cloud;Servicios de red para Bare Metal Cloud;Services réseau Bare Metal Cloud;Servizi di rete Bare Metal Cloud;Usługi sieciowe Bare Metal Cloud;Serviços de rede Bare Metal Cloud +Cloud Web 2;Cloud Web 2;Cloud Web 2;Cloud Web 2;Cloud Web 2;Cloud Web 2;Cloud Web 2 +Billing Control;Billing Control;Billing Control;Billing control;Billing Control;Billing Control;Billing Control +HA-NAS;HA-NAS;NAS-HA;NAS-HA;NAS-HA;NAS-HA;NAS-HA +;graphical console;;console graphique;;; +Compute;Compute;Compute;Compute;Compute;Compute;Compute +Backup Storage;Backup Storage;Backup Storage;Backup Storage;Backup Storage;Backup Storage;Backup Storage +Managed Bare Metal;Managed Bare Metal;Managed Bare Metal;Managed Bare Metal;Managed Bare Metal;Managed Bare Metal;Managed Bare Metal +Cloud Web 3;Cloud Web 3;Cloud Web 3;Cloud Web 3;Cloud Web 3;Cloud Web 3;Cloud Web 3 +SSL-Zertifikat „Sectigo EV“;Sectigo EV SSL certificate;Certificado SSL Sectigo EV;Certificat SSL Sectigo EV;Certificato SSL Sectigo EV;Certyfikat SSL Sectigo EV;Certificado SSL Sectigo EV +OpenStack Orchestration;OpenStack Orchestration;OpenStack Orchestration;OpenStack Orchestration;OpenStack Orchestration;OpenStack Orchestration;OpenStack Orchestration +;Registrant;;Titulaire;;; +Block Storage;Block Storage;Block Storage;Block Storage;Block Storage;Block Storage;Block Storage +;reseller;;revendeur;;; +User and Role Management;User and Role Management;User and Role Management;User and role management;User and Role Management;User and Role Management;User and Role Management +;;;conditions générales de service;;Ogólne warunki świadczenia usługi; +;sub-processor;;sous-traitant ultérieur;;; +Professional Services;Professional Services;Professional Services;Professional Services;Professional Services;Professional Services;Professional Services +SSL Gateway;SSL Gateway;SSL Gateway;SSL Gateway;SSL Gateway;SSL Gateway;SSL Gateway +M3 Aggregator;M3 Aggregator;M3 Aggregator;M3 Aggregator;M3 Aggregator;M3 Aggregator;M3 Aggregator +;tape storage;;archivage sur bande;;; +VMware on OVHcloud;VMware on OVHcloud;VMware on OVHcloud;VMware on OVHcloud;VMware on OVHcloud;VMware on OVHcloud;VMware on OVHcloud +Private SQL-Datenbanken;Private SQL Databases;Bases de datos SQL Privado;Bases de données SQL Privé;Database SQL Privato;Bazy danych Private SQL;Bases de dados SQL Privado +Workflow Management;Workflow Management;Workflow Management;Workflow management;Workflow Management;Workflow Management;Workflow Management +;Databases;Databases;Databases;Database;Databases;Databases +Essential;Essential;Essential;Essential;Essential;Essential;Essential +High Speed Gen2 Block Storage;High Speed Gen2 Block Storage;High Speed Gen2;High Speed Gen2 Block Storage;High Speed Gen2;High Speed Gen2 Block Storage;High Speed Gen2 Block Storage +;Registry operators;;Registres opérateurs;;; +OVHcloud Startup Program;OVHcloud Startup Program;OVHcloud Startup Program;Startup program;OVHcloud Startup Program;OVHcloud Startup Program;OVHcloud Startup Program +Premium Support;Premium Support;Soporte Premium;Support Premium;Supporto Premium;Premium;Suporte Premium +;;;Public VCF as-a-Service;;Public VCF as a Service; +;;;Web Cloud;;Web Cloud; +Game DDoS-Schutz;Anti-DDoS Game;Anti-DDoS Game;Anti-DDoS Game;Anti-DDoS Game;Anty-DDoS Game;Anti-DDoS Game +NSX Edge-Dienste;NSX Edge Services;Servicios NSX Edge;Services NSX Edge;Servizi NSX Edge;NSX Edge Services;Serviços NSX Edge +;Containers and Orchestration;Containers & Orchestration;Containers and orchestration;Containers and Orchestration;Containers & Orchestration;Containers & Orchestration \ No newline at end of file diff --git a/pages/network/load_balancer/case_blue_green/guide.en-asia.md b/pages/network/load_balancer/case_blue_green/guide.en-asia.md index 903379d1e2f..60c95ac97a0 100644 --- a/pages/network/load_balancer/case_blue_green/guide.en-asia.md +++ b/pages/network/load_balancer/case_blue_green/guide.en-asia.md @@ -1,7 +1,7 @@ --- title: 'Deploying a blue-green infrastructure' excerpt: 'This guide will show you how to deploy a blue-green infrastructure with the OVHcloud Load Balancer' -updated: 2025-10-23 +updated: 2025-10-24 --- ## Objective diff --git a/pages/network/load_balancer/case_blue_green/guide.en-au.md b/pages/network/load_balancer/case_blue_green/guide.en-au.md index 903379d1e2f..60c95ac97a0 100644 --- a/pages/network/load_balancer/case_blue_green/guide.en-au.md +++ b/pages/network/load_balancer/case_blue_green/guide.en-au.md @@ -1,7 +1,7 @@ --- title: 'Deploying a blue-green infrastructure' excerpt: 'This guide will show you how to deploy a blue-green infrastructure with the OVHcloud Load Balancer' -updated: 2025-10-23 +updated: 2025-10-24 --- ## Objective diff --git a/pages/network/load_balancer/case_blue_green/guide.en-ca.md b/pages/network/load_balancer/case_blue_green/guide.en-ca.md index 903379d1e2f..60c95ac97a0 100644 --- a/pages/network/load_balancer/case_blue_green/guide.en-ca.md +++ b/pages/network/load_balancer/case_blue_green/guide.en-ca.md @@ -1,7 +1,7 @@ --- title: 'Deploying a blue-green infrastructure' excerpt: 'This guide will show you how to deploy a blue-green infrastructure with the OVHcloud Load Balancer' -updated: 2025-10-23 +updated: 2025-10-24 --- ## Objective diff --git a/pages/network/load_balancer/case_blue_green/guide.en-gb.md b/pages/network/load_balancer/case_blue_green/guide.en-gb.md index 903379d1e2f..60c95ac97a0 100644 --- a/pages/network/load_balancer/case_blue_green/guide.en-gb.md +++ b/pages/network/load_balancer/case_blue_green/guide.en-gb.md @@ -1,7 +1,7 @@ --- title: 'Deploying a blue-green infrastructure' excerpt: 'This guide will show you how to deploy a blue-green infrastructure with the OVHcloud Load Balancer' -updated: 2025-10-23 +updated: 2025-10-24 --- ## Objective diff --git a/pages/network/load_balancer/case_blue_green/guide.en-sg.md b/pages/network/load_balancer/case_blue_green/guide.en-sg.md index 903379d1e2f..60c95ac97a0 100644 --- a/pages/network/load_balancer/case_blue_green/guide.en-sg.md +++ b/pages/network/load_balancer/case_blue_green/guide.en-sg.md @@ -1,7 +1,7 @@ --- title: 'Deploying a blue-green infrastructure' excerpt: 'This guide will show you how to deploy a blue-green infrastructure with the OVHcloud Load Balancer' -updated: 2025-10-23 +updated: 2025-10-24 --- ## Objective diff --git a/pages/network/load_balancer/case_blue_green/guide.en-us.md b/pages/network/load_balancer/case_blue_green/guide.en-us.md index 903379d1e2f..60c95ac97a0 100644 --- a/pages/network/load_balancer/case_blue_green/guide.en-us.md +++ b/pages/network/load_balancer/case_blue_green/guide.en-us.md @@ -1,7 +1,7 @@ --- title: 'Deploying a blue-green infrastructure' excerpt: 'This guide will show you how to deploy a blue-green infrastructure with the OVHcloud Load Balancer' -updated: 2025-10-23 +updated: 2025-10-24 --- ## Objective diff --git a/pages/network/load_balancer/case_blue_green/guide.fr-ca.md b/pages/network/load_balancer/case_blue_green/guide.fr-ca.md index 2fae96fee2c..36313db60a0 100644 --- a/pages/network/load_balancer/case_blue_green/guide.fr-ca.md +++ b/pages/network/load_balancer/case_blue_green/guide.fr-ca.md @@ -1,7 +1,7 @@ --- title: "Déploiement d'une infrastructure blue-green" excerpt: "Ce guide vous montre comment déployer une infrastructure blue-green avec le Load Balancer OVHcloud" -updated: 2025-10-23 +updated: 2025-10-24 --- ## Objectif @@ -36,7 +36,7 @@ Le principe d'un déploiement **blue-green** implique de pouvoir basculer facile Dans ce scénario, votre service Load Balancer joue un rôle central. C'est l'élément que vous utilisez pour exposer simultanément vos deux infrastructures (production et développement) à différents utilisateurs. -L'infrastructure de production est accessible par vos clients sur le service HTTP standard (port 80), et votre infrastructure de développement est accessible par les développeurs et administrateurs sur le port non standard 8888. +L'infrastructure de production est accessible pour vos clients sur le service HTTP standard (port 80), et votre infrastructure de développement est accessible pour les développeurs et administrateurs sur le port non standard 8888. Au cours de la phase de configuration initiale, les rôles sont provisoirement attribués à chaque composant de l'infrastructure. **L'infrastructure A** sert d'environnement de production initial, tandis que **l'infrastructure B** sert d'environnement de staging. À ce stade, nous allons les considérer comme similaires l'une à l'autre. @@ -50,7 +50,7 @@ Le schéma ci-dessous donne une idée générale de l'architecture : Cette infrastructure est composée d'une ferme de serveurs qui sera associée plus tard à un front-end de votre Load Balancer. Cette ferme exposera un service HTTP, TCP ou UDP au front-end. Elle assure également l'équilibrage de charge en envoyant le trafic entrant du front-end aux serveurs. Pour plus de détails sur le rôle des différents composants du service Load Balancer OVHcloud, vous pouvez lire le guide suivant : [Présentation du service OVHcloud Load Balancer ](/pages/network/load_balancer/use_presentation). -Dans notre scénario, nous allons déclarer une ferme de serveurs pour le service HTTP. Veuillez noter que vous pouvez créer autant de fermes (ainsi que de services TCP et/ou UDP) que nécessaire pour que votre service final soit accessible à vos clients. +Dans notre scénario, nous allons déclarer une ferme de serveurs pour le service HTTP. Veuillez noter que vous pouvez créer autant de fermes (ainsi que de services TCP et/ou UDP) que nécessaire pour que votre service final soit accessible pour vos clients. #### Via l'espace client OVHcloud @@ -303,7 +303,7 @@ Voici le résultat attendu dans l'espace client OVHcloud après la mise à jour |frontendId|Votre ID de front-end de production|70090| |defaultFarmId|Votre ID de ferme de serveurs de développement|77212| -#### Pour appliquer vos modifications et basculer effectivement les environnements de production et de développement +#### Appliquer vos modifications et basculer effectivement les environnements de production et de développement > [!api] > diff --git a/pages/network/load_balancer/case_blue_green/guide.fr-fr.md b/pages/network/load_balancer/case_blue_green/guide.fr-fr.md index 2fae96fee2c..36313db60a0 100644 --- a/pages/network/load_balancer/case_blue_green/guide.fr-fr.md +++ b/pages/network/load_balancer/case_blue_green/guide.fr-fr.md @@ -1,7 +1,7 @@ --- title: "Déploiement d'une infrastructure blue-green" excerpt: "Ce guide vous montre comment déployer une infrastructure blue-green avec le Load Balancer OVHcloud" -updated: 2025-10-23 +updated: 2025-10-24 --- ## Objectif @@ -36,7 +36,7 @@ Le principe d'un déploiement **blue-green** implique de pouvoir basculer facile Dans ce scénario, votre service Load Balancer joue un rôle central. C'est l'élément que vous utilisez pour exposer simultanément vos deux infrastructures (production et développement) à différents utilisateurs. -L'infrastructure de production est accessible par vos clients sur le service HTTP standard (port 80), et votre infrastructure de développement est accessible par les développeurs et administrateurs sur le port non standard 8888. +L'infrastructure de production est accessible pour vos clients sur le service HTTP standard (port 80), et votre infrastructure de développement est accessible pour les développeurs et administrateurs sur le port non standard 8888. Au cours de la phase de configuration initiale, les rôles sont provisoirement attribués à chaque composant de l'infrastructure. **L'infrastructure A** sert d'environnement de production initial, tandis que **l'infrastructure B** sert d'environnement de staging. À ce stade, nous allons les considérer comme similaires l'une à l'autre. @@ -50,7 +50,7 @@ Le schéma ci-dessous donne une idée générale de l'architecture : Cette infrastructure est composée d'une ferme de serveurs qui sera associée plus tard à un front-end de votre Load Balancer. Cette ferme exposera un service HTTP, TCP ou UDP au front-end. Elle assure également l'équilibrage de charge en envoyant le trafic entrant du front-end aux serveurs. Pour plus de détails sur le rôle des différents composants du service Load Balancer OVHcloud, vous pouvez lire le guide suivant : [Présentation du service OVHcloud Load Balancer ](/pages/network/load_balancer/use_presentation). -Dans notre scénario, nous allons déclarer une ferme de serveurs pour le service HTTP. Veuillez noter que vous pouvez créer autant de fermes (ainsi que de services TCP et/ou UDP) que nécessaire pour que votre service final soit accessible à vos clients. +Dans notre scénario, nous allons déclarer une ferme de serveurs pour le service HTTP. Veuillez noter que vous pouvez créer autant de fermes (ainsi que de services TCP et/ou UDP) que nécessaire pour que votre service final soit accessible pour vos clients. #### Via l'espace client OVHcloud @@ -303,7 +303,7 @@ Voici le résultat attendu dans l'espace client OVHcloud après la mise à jour |frontendId|Votre ID de front-end de production|70090| |defaultFarmId|Votre ID de ferme de serveurs de développement|77212| -#### Pour appliquer vos modifications et basculer effectivement les environnements de production et de développement +#### Appliquer vos modifications et basculer effectivement les environnements de production et de développement > [!api] > diff --git a/pages/network/load_balancer/case_smtp/guide.en-asia.md b/pages/network/load_balancer/case_smtp/guide.en-asia.md index 81712ab5352..6ff6bd90aa2 100644 --- a/pages/network/load_balancer/case_smtp/guide.en-asia.md +++ b/pages/network/load_balancer/case_smtp/guide.en-asia.md @@ -1,71 +1,67 @@ --- -title: 'Configuring SMTP on a Load Balancer service' -excerpt: 'Find out how to use SMTP with the OVH Load Balancer' -updated: 2018-12-28 +title: 'How to configure SMTP on a Load Balancer service' +excerpt: 'Find out how to use SMTP with the OVHcloud Load Balancer' +updated: 2025-10-24 --- ## Objective -In this guide, we will configure a basic TCP load balancing service, for one or more SMTP servers. A TCP front-end will listen to TCP traffic on port 25. It is configured to direct traffic to a TCP farm with one or more TCP servers, depending on how you choose to configure it. +**This guide outlines how to configure the OVHcloud Load Balancer to distribute traffic across multiple SMTP servers.** -**This guide is designed to help you configure an OVH Load Balancer service in order to balance load across several servers that respond in SMTP.** +## Requirements -> [!warning] -> -> Questions on what an SMTP service is and how it works will not be covered here. This guide is aimed at readers who have a general understanding of SMTP, or practical experience with it. -> +- An [OVHcloud Load balancer](/links/network/load-balancer) service in your OVHcloud account. +- Access to the [OVHcloud Control Panel](/links/manager). +- A Postfix-type SMTP service installed and configured on your servers. -> [!warning] -> -> We will assume that you already have a Postfix SMTP service set up and configured your servers. -> +## Instructions > [!warning] > -> This guide will take you through the steps required. Depending on the way you have designed your architecture, some configurations may vary. +> This guide assumes a working knowledge of SMTP protocol and service operation. > -As a reminder, each protocol (HTTP, TCP and UDP) in the OVH Load Balancer service has its own associated front-ends, farms and servers. +As a reminder, each protocol (HTTP, TCP and UDP) in the OVHcloud Load Balancer service has its own associated front-ends, farms and servers. > [!warning] > -> The order in which elements are created is important. In particular, the server farms must be configured before we can attach servers to them. +> The order in which elements are created is important. In particular, the server farms must be configured before servers can be attached to them. > -In the Sunrise Control Panel, you will see the features detailed below: +In the Control Panel, you will see the features detailed below: -![OVH Load Balancer service](images/iplb_service.png){.thumbnail} +![OVHcloud Load Balancer service](images/iplb_service.png){.thumbnail} -Via the OVH API, in the section: +Via the OVHcloud API, use the following call: > [!api] > > @api {v1} /ipLoadbalancing GET /ipLoadbalancing > -For more information on the API’s features, you can refer to the following guide: [Load Balancer API Quick Reference](/pages/network/load_balancer/use_api_reference){.ref} +For more information on the API features, you can refer to [the following guide](/pages/network/load_balancer/use_api_reference). -## Add a server farm. +### Add a server farm -We will add a farm of TCP servers to our service, which is the part that balances traffic on the servers. +A TCP server farm must be added to the service; this component manages traffic balancing across the servers. -### Via the Sunrise Control Panel. +#### Via the OVHcloud Control Panel In the `Farms`{.action} tab for servers, click on the `+TCP/TLS`{.action} button. -Fill in the fields. The mandatory fields for a basic configuration are *Port* and *Zone*. In our case, for SMTP, port 25 is used. If no ports are specified, your OVH Load Balancer will automatically use the same port as the corresponding front-end. +Fill in the fields. The mandatory fields for a basic configuration are *Port* and *Zone*. For SMTP, port 25 is used. If no ports are specified, your OVHcloud Load Balancer will automatically use the same port as the corresponding front-end. -As an option, you can add an SMTP probe on your farm. +Optionally, you can add an SMTP probe on your farm. ![Add a server farm via the Control Panel](images/add_farm.png){.thumbnail} -Click `Add`{.action} once you have filled in the fields. +Click on `Add`{.action} once you have filled in the fields. Your server farm should appear in the list, in the `Farms`{.action} tab. ![Details of the server farm created](images/resume_farm.png){.thumbnail} -### Via the API +#### Via the OVHcloud API - List of TCP server farms: @@ -74,7 +70,7 @@ Your server farm should appear in the list, in the `Farms`{.action} tab. > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/tcp/farm > -- Details of a specific TCP server: +- Details of a specific TCP server farm: > [!api] > @@ -102,30 +98,30 @@ Your server farm should appear in the list, in the `Farms`{.action} tab. > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/tcp/farm/{farmId} > -## Add a server. +### Add a server -We will now add a server to our server farm. +A server must now be added to the server farm. -### Via the Sunrise Control Panel. +#### Via the OVHcloud Control Panel -In the `Farms`{.action} tab, select the farm you want to add a server to by clicking on the corresponding line. The list of servers already configured in the farm will appear beneath the list of farms, along with the `Add a server`{.action} button. Click on this button to add a new server. +In the `Farms`{.action} tab, select the farm you want to add a server to by clicking on the corresponding line. The list of servers already configured in the farm will appear beneath the list of farms, along with the `Add a server`{.action} button. Click this button to add a new server. -Only the *IPv4 address*, *Status* and *ProxyProtocol version* fields are mandatory. If a server does not use the same port as the one defined earlier in the farm, you may overload it by configuring a server. However, to keep the configuration as standard as possible and easy to maintain, we recommend only using this parameter in advanced cases. +The mandatory fields are the *IPv4 address*, *Status*, and *ProxyProtocol version*. If a server port is configured, it will override the port defined in the farm. To keep the configuration as standard as possible and easy to maintain, we recommend only using this parameter in advanced cases. > [!warning] > -> It is important to configure ProxyProtocol in version v1, so that you can get the real source IP on your SMTP service. Postfix is compatible with this protocol. +> It is important to configure ProxyProtocol in version v1 so that you can retrieve the real source IP on your SMTP service. Postfix is compatible with this protocol. > ![Add a server to a farm.](images/add_server.png){.thumbnail} -Click `Add`{.action} once you have filled in the fields. +Click on `Add`{.action} once you have filled in the fields. Your server should appear in the server list, in the `Farms`{.action} tab, just below the list of farms. ![Details of the server created.](images/resume_server.png){.thumbnail} -### Via the API +#### Via the OVHcloud API - List of servers in the farm: @@ -162,29 +158,29 @@ Your server should appear in the server list, in the `Farms`{.action} tab, just > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/tcp/farm/{farmId}/server > -## Add a front-end +### Add a front-end -We will now add a `front-end`{.action} to our service, and connect it to our server farm. The front-end is the part of your OVH Load Balancer that exposes your service on the internet. +A `front-end`{.action} must now be added to the service and connected to the server farm. The front-end is the component of your OVHcloud Load Balancer that exposes your service to the internet. -### Via the Sunrise Control Panel. +#### Via the OVHcloud Control Panel Go to the `+ Front-ends`{.action} tab, and click `+TCP/TLS`{.action}. -Fill in the fields. The only mandatory fields for a basic configuration are *Port* (25 for a standard SMTP service), *Zone* and *Probe*, if you configured a probe on your farm. If you want your service to be available across several ports at once, you can specify a list of ports, separated by commas, or a range of ports, in the format "start_port-end_port". +Fill in the fields. The mandatory fields for a basic configuration are *Port* (25 for a standard SMTP service), *Zone*, *Default farm* and *Probe* (if a probe was configured on your farm). If you want your service to be available across several ports at once, you can specify a list of ports, separated by commas, or a port range, in the format "-". -If you have routed Additional IPs to your OVH Load Balancer service, you can also attach a front-end to one or more specific Additional IPs. +If you have routed Additional IPs to your OVHcloud Load Balancer service, you can also attach a front-end to one or more specific Additional IPs. -Please remember to specify the farm you created earlier as a “default farm”. +Ensure the farm you created earlier is specified as the “default farm”. ![Add a front-end](images/add_frontend.png){.thumbnail} -Click `Add`{.action} once you have filled in the fields. +Click `Add`{.action} once the fields are filled. Your front-end must appear in the list, in the `Front-ends`{.action} tab. ![Details of the front-end created](images/resume_frontend.png){.thumbnail} -### Via the API +#### Via the OVHcloud API - List of TCP front-ends: @@ -221,17 +217,17 @@ Your front-end must appear in the list, in the `Front-ends`{.action} tab. > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/tcp/frontend/{frontendId} > -## Apply the modifications +### Apply the modifications -The modifications made to your OVH Load Balancer must be *explicitly applied* in each of the zones configured for your service. Only at this point will they be visible to your website visitors. This way, you can make complex configuration changes several times, and only apply them once the configuration is ready. +Modifications made to your OVHcloud Load Balancer must be **explicitly applied** in each of the zones configured for your service. They will only become visible to your users at this point. This process allows for complex configuration changes to be prepared and applied only when fully ready. -If you have several zones, you must apply the same configuration for each of them. +If you have several zones, the same configuration must be applied to each. -### Via the Sunrise Control Panel. +#### Via the OVHcloud Control Panel -Go the homepage for the OVH Load Balancer, and click `Apply:Zone`{.action} for each of the zones concerned. +Go to the homepage for the OVHcloud Load Balancer, and click `Apply:Zone`{.action} for each of the zones concerned. -### Via the API. +#### Via the OVHcloud API - Refresh a zone: @@ -240,21 +236,22 @@ Go the homepage for the OVH Load Balancer, and click `Apply:Zone`{.action} for e > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh > -## Postfix configuration. +### Postfix configuration To make Postfix compatible with HAProxy *ProxyProtocol*, an option is required in the postfix main.cf configuration file: -**smtp_upstream_proxy_protocol = haproxy** +```bash +smtp_upstream_proxy_protocol = haproxy +``` -You then need to restart your Postfix daemon. +The Postfix daemon must then be restarted. -## Confirmation. +### Confirmation -After you have completed all of these steps, you should now have a functional Load Balancer service for your SMTP servers. You can now check the service status by requesting your IP Load Balancer as an SMTP server. +Upon completing these steps, you will have a functional Load Balancer service for your SMTP servers. The service status can now be checked by requesting your IP Load Balancer as an SMTP server. ![Connection to SMTP via telnet](images/resume_validate.png){.thumbnail} ## Go further -Join our community of users on . - +Join our [community of users](/links/community). diff --git a/pages/network/load_balancer/case_smtp/guide.en-ca.md b/pages/network/load_balancer/case_smtp/guide.en-ca.md index 81712ab5352..6ff6bd90aa2 100644 --- a/pages/network/load_balancer/case_smtp/guide.en-ca.md +++ b/pages/network/load_balancer/case_smtp/guide.en-ca.md @@ -1,71 +1,67 @@ --- -title: 'Configuring SMTP on a Load Balancer service' -excerpt: 'Find out how to use SMTP with the OVH Load Balancer' -updated: 2018-12-28 +title: 'How to configure SMTP on a Load Balancer service' +excerpt: 'Find out how to use SMTP with the OVHcloud Load Balancer' +updated: 2025-10-24 --- ## Objective -In this guide, we will configure a basic TCP load balancing service, for one or more SMTP servers. A TCP front-end will listen to TCP traffic on port 25. It is configured to direct traffic to a TCP farm with one or more TCP servers, depending on how you choose to configure it. +**This guide outlines how to configure the OVHcloud Load Balancer to distribute traffic across multiple SMTP servers.** -**This guide is designed to help you configure an OVH Load Balancer service in order to balance load across several servers that respond in SMTP.** +## Requirements -> [!warning] -> -> Questions on what an SMTP service is and how it works will not be covered here. This guide is aimed at readers who have a general understanding of SMTP, or practical experience with it. -> +- An [OVHcloud Load balancer](/links/network/load-balancer) service in your OVHcloud account. +- Access to the [OVHcloud Control Panel](/links/manager). +- A Postfix-type SMTP service installed and configured on your servers. -> [!warning] -> -> We will assume that you already have a Postfix SMTP service set up and configured your servers. -> +## Instructions > [!warning] > -> This guide will take you through the steps required. Depending on the way you have designed your architecture, some configurations may vary. +> This guide assumes a working knowledge of SMTP protocol and service operation. > -As a reminder, each protocol (HTTP, TCP and UDP) in the OVH Load Balancer service has its own associated front-ends, farms and servers. +As a reminder, each protocol (HTTP, TCP and UDP) in the OVHcloud Load Balancer service has its own associated front-ends, farms and servers. > [!warning] > -> The order in which elements are created is important. In particular, the server farms must be configured before we can attach servers to them. +> The order in which elements are created is important. In particular, the server farms must be configured before servers can be attached to them. > -In the Sunrise Control Panel, you will see the features detailed below: +In the Control Panel, you will see the features detailed below: -![OVH Load Balancer service](images/iplb_service.png){.thumbnail} +![OVHcloud Load Balancer service](images/iplb_service.png){.thumbnail} -Via the OVH API, in the section: +Via the OVHcloud API, use the following call: > [!api] > > @api {v1} /ipLoadbalancing GET /ipLoadbalancing > -For more information on the API’s features, you can refer to the following guide: [Load Balancer API Quick Reference](/pages/network/load_balancer/use_api_reference){.ref} +For more information on the API features, you can refer to [the following guide](/pages/network/load_balancer/use_api_reference). -## Add a server farm. +### Add a server farm -We will add a farm of TCP servers to our service, which is the part that balances traffic on the servers. +A TCP server farm must be added to the service; this component manages traffic balancing across the servers. -### Via the Sunrise Control Panel. +#### Via the OVHcloud Control Panel In the `Farms`{.action} tab for servers, click on the `+TCP/TLS`{.action} button. -Fill in the fields. The mandatory fields for a basic configuration are *Port* and *Zone*. In our case, for SMTP, port 25 is used. If no ports are specified, your OVH Load Balancer will automatically use the same port as the corresponding front-end. +Fill in the fields. The mandatory fields for a basic configuration are *Port* and *Zone*. For SMTP, port 25 is used. If no ports are specified, your OVHcloud Load Balancer will automatically use the same port as the corresponding front-end. -As an option, you can add an SMTP probe on your farm. +Optionally, you can add an SMTP probe on your farm. ![Add a server farm via the Control Panel](images/add_farm.png){.thumbnail} -Click `Add`{.action} once you have filled in the fields. +Click on `Add`{.action} once you have filled in the fields. Your server farm should appear in the list, in the `Farms`{.action} tab. ![Details of the server farm created](images/resume_farm.png){.thumbnail} -### Via the API +#### Via the OVHcloud API - List of TCP server farms: @@ -74,7 +70,7 @@ Your server farm should appear in the list, in the `Farms`{.action} tab. > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/tcp/farm > -- Details of a specific TCP server: +- Details of a specific TCP server farm: > [!api] > @@ -102,30 +98,30 @@ Your server farm should appear in the list, in the `Farms`{.action} tab. > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/tcp/farm/{farmId} > -## Add a server. +### Add a server -We will now add a server to our server farm. +A server must now be added to the server farm. -### Via the Sunrise Control Panel. +#### Via the OVHcloud Control Panel -In the `Farms`{.action} tab, select the farm you want to add a server to by clicking on the corresponding line. The list of servers already configured in the farm will appear beneath the list of farms, along with the `Add a server`{.action} button. Click on this button to add a new server. +In the `Farms`{.action} tab, select the farm you want to add a server to by clicking on the corresponding line. The list of servers already configured in the farm will appear beneath the list of farms, along with the `Add a server`{.action} button. Click this button to add a new server. -Only the *IPv4 address*, *Status* and *ProxyProtocol version* fields are mandatory. If a server does not use the same port as the one defined earlier in the farm, you may overload it by configuring a server. However, to keep the configuration as standard as possible and easy to maintain, we recommend only using this parameter in advanced cases. +The mandatory fields are the *IPv4 address*, *Status*, and *ProxyProtocol version*. If a server port is configured, it will override the port defined in the farm. To keep the configuration as standard as possible and easy to maintain, we recommend only using this parameter in advanced cases. > [!warning] > -> It is important to configure ProxyProtocol in version v1, so that you can get the real source IP on your SMTP service. Postfix is compatible with this protocol. +> It is important to configure ProxyProtocol in version v1 so that you can retrieve the real source IP on your SMTP service. Postfix is compatible with this protocol. > ![Add a server to a farm.](images/add_server.png){.thumbnail} -Click `Add`{.action} once you have filled in the fields. +Click on `Add`{.action} once you have filled in the fields. Your server should appear in the server list, in the `Farms`{.action} tab, just below the list of farms. ![Details of the server created.](images/resume_server.png){.thumbnail} -### Via the API +#### Via the OVHcloud API - List of servers in the farm: @@ -162,29 +158,29 @@ Your server should appear in the server list, in the `Farms`{.action} tab, just > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/tcp/farm/{farmId}/server > -## Add a front-end +### Add a front-end -We will now add a `front-end`{.action} to our service, and connect it to our server farm. The front-end is the part of your OVH Load Balancer that exposes your service on the internet. +A `front-end`{.action} must now be added to the service and connected to the server farm. The front-end is the component of your OVHcloud Load Balancer that exposes your service to the internet. -### Via the Sunrise Control Panel. +#### Via the OVHcloud Control Panel Go to the `+ Front-ends`{.action} tab, and click `+TCP/TLS`{.action}. -Fill in the fields. The only mandatory fields for a basic configuration are *Port* (25 for a standard SMTP service), *Zone* and *Probe*, if you configured a probe on your farm. If you want your service to be available across several ports at once, you can specify a list of ports, separated by commas, or a range of ports, in the format "start_port-end_port". +Fill in the fields. The mandatory fields for a basic configuration are *Port* (25 for a standard SMTP service), *Zone*, *Default farm* and *Probe* (if a probe was configured on your farm). If you want your service to be available across several ports at once, you can specify a list of ports, separated by commas, or a port range, in the format "-". -If you have routed Additional IPs to your OVH Load Balancer service, you can also attach a front-end to one or more specific Additional IPs. +If you have routed Additional IPs to your OVHcloud Load Balancer service, you can also attach a front-end to one or more specific Additional IPs. -Please remember to specify the farm you created earlier as a “default farm”. +Ensure the farm you created earlier is specified as the “default farm”. ![Add a front-end](images/add_frontend.png){.thumbnail} -Click `Add`{.action} once you have filled in the fields. +Click `Add`{.action} once the fields are filled. Your front-end must appear in the list, in the `Front-ends`{.action} tab. ![Details of the front-end created](images/resume_frontend.png){.thumbnail} -### Via the API +#### Via the OVHcloud API - List of TCP front-ends: @@ -221,17 +217,17 @@ Your front-end must appear in the list, in the `Front-ends`{.action} tab. > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/tcp/frontend/{frontendId} > -## Apply the modifications +### Apply the modifications -The modifications made to your OVH Load Balancer must be *explicitly applied* in each of the zones configured for your service. Only at this point will they be visible to your website visitors. This way, you can make complex configuration changes several times, and only apply them once the configuration is ready. +Modifications made to your OVHcloud Load Balancer must be **explicitly applied** in each of the zones configured for your service. They will only become visible to your users at this point. This process allows for complex configuration changes to be prepared and applied only when fully ready. -If you have several zones, you must apply the same configuration for each of them. +If you have several zones, the same configuration must be applied to each. -### Via the Sunrise Control Panel. +#### Via the OVHcloud Control Panel -Go the homepage for the OVH Load Balancer, and click `Apply:Zone`{.action} for each of the zones concerned. +Go to the homepage for the OVHcloud Load Balancer, and click `Apply:Zone`{.action} for each of the zones concerned. -### Via the API. +#### Via the OVHcloud API - Refresh a zone: @@ -240,21 +236,22 @@ Go the homepage for the OVH Load Balancer, and click `Apply:Zone`{.action} for e > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh > -## Postfix configuration. +### Postfix configuration To make Postfix compatible with HAProxy *ProxyProtocol*, an option is required in the postfix main.cf configuration file: -**smtp_upstream_proxy_protocol = haproxy** +```bash +smtp_upstream_proxy_protocol = haproxy +``` -You then need to restart your Postfix daemon. +The Postfix daemon must then be restarted. -## Confirmation. +### Confirmation -After you have completed all of these steps, you should now have a functional Load Balancer service for your SMTP servers. You can now check the service status by requesting your IP Load Balancer as an SMTP server. +Upon completing these steps, you will have a functional Load Balancer service for your SMTP servers. The service status can now be checked by requesting your IP Load Balancer as an SMTP server. ![Connection to SMTP via telnet](images/resume_validate.png){.thumbnail} ## Go further -Join our community of users on . - +Join our [community of users](/links/community). diff --git a/pages/network/load_balancer/case_smtp/guide.en-gb.md b/pages/network/load_balancer/case_smtp/guide.en-gb.md index e905e73bc45..6ff6bd90aa2 100644 --- a/pages/network/load_balancer/case_smtp/guide.en-gb.md +++ b/pages/network/load_balancer/case_smtp/guide.en-gb.md @@ -1,7 +1,7 @@ --- title: 'How to configure SMTP on a Load Balancer service' excerpt: 'Find out how to use SMTP with the OVHcloud Load Balancer' -updated: 2025-10-21 +updated: 2025-10-24 --- ## Objective diff --git a/pages/network/load_balancer/case_smtp/guide.en-sg.md b/pages/network/load_balancer/case_smtp/guide.en-sg.md index 81712ab5352..6ff6bd90aa2 100644 --- a/pages/network/load_balancer/case_smtp/guide.en-sg.md +++ b/pages/network/load_balancer/case_smtp/guide.en-sg.md @@ -1,71 +1,67 @@ --- -title: 'Configuring SMTP on a Load Balancer service' -excerpt: 'Find out how to use SMTP with the OVH Load Balancer' -updated: 2018-12-28 +title: 'How to configure SMTP on a Load Balancer service' +excerpt: 'Find out how to use SMTP with the OVHcloud Load Balancer' +updated: 2025-10-24 --- ## Objective -In this guide, we will configure a basic TCP load balancing service, for one or more SMTP servers. A TCP front-end will listen to TCP traffic on port 25. It is configured to direct traffic to a TCP farm with one or more TCP servers, depending on how you choose to configure it. +**This guide outlines how to configure the OVHcloud Load Balancer to distribute traffic across multiple SMTP servers.** -**This guide is designed to help you configure an OVH Load Balancer service in order to balance load across several servers that respond in SMTP.** +## Requirements -> [!warning] -> -> Questions on what an SMTP service is and how it works will not be covered here. This guide is aimed at readers who have a general understanding of SMTP, or practical experience with it. -> +- An [OVHcloud Load balancer](/links/network/load-balancer) service in your OVHcloud account. +- Access to the [OVHcloud Control Panel](/links/manager). +- A Postfix-type SMTP service installed and configured on your servers. -> [!warning] -> -> We will assume that you already have a Postfix SMTP service set up and configured your servers. -> +## Instructions > [!warning] > -> This guide will take you through the steps required. Depending on the way you have designed your architecture, some configurations may vary. +> This guide assumes a working knowledge of SMTP protocol and service operation. > -As a reminder, each protocol (HTTP, TCP and UDP) in the OVH Load Balancer service has its own associated front-ends, farms and servers. +As a reminder, each protocol (HTTP, TCP and UDP) in the OVHcloud Load Balancer service has its own associated front-ends, farms and servers. > [!warning] > -> The order in which elements are created is important. In particular, the server farms must be configured before we can attach servers to them. +> The order in which elements are created is important. In particular, the server farms must be configured before servers can be attached to them. > -In the Sunrise Control Panel, you will see the features detailed below: +In the Control Panel, you will see the features detailed below: -![OVH Load Balancer service](images/iplb_service.png){.thumbnail} +![OVHcloud Load Balancer service](images/iplb_service.png){.thumbnail} -Via the OVH API, in the section: +Via the OVHcloud API, use the following call: > [!api] > > @api {v1} /ipLoadbalancing GET /ipLoadbalancing > -For more information on the API’s features, you can refer to the following guide: [Load Balancer API Quick Reference](/pages/network/load_balancer/use_api_reference){.ref} +For more information on the API features, you can refer to [the following guide](/pages/network/load_balancer/use_api_reference). -## Add a server farm. +### Add a server farm -We will add a farm of TCP servers to our service, which is the part that balances traffic on the servers. +A TCP server farm must be added to the service; this component manages traffic balancing across the servers. -### Via the Sunrise Control Panel. +#### Via the OVHcloud Control Panel In the `Farms`{.action} tab for servers, click on the `+TCP/TLS`{.action} button. -Fill in the fields. The mandatory fields for a basic configuration are *Port* and *Zone*. In our case, for SMTP, port 25 is used. If no ports are specified, your OVH Load Balancer will automatically use the same port as the corresponding front-end. +Fill in the fields. The mandatory fields for a basic configuration are *Port* and *Zone*. For SMTP, port 25 is used. If no ports are specified, your OVHcloud Load Balancer will automatically use the same port as the corresponding front-end. -As an option, you can add an SMTP probe on your farm. +Optionally, you can add an SMTP probe on your farm. ![Add a server farm via the Control Panel](images/add_farm.png){.thumbnail} -Click `Add`{.action} once you have filled in the fields. +Click on `Add`{.action} once you have filled in the fields. Your server farm should appear in the list, in the `Farms`{.action} tab. ![Details of the server farm created](images/resume_farm.png){.thumbnail} -### Via the API +#### Via the OVHcloud API - List of TCP server farms: @@ -74,7 +70,7 @@ Your server farm should appear in the list, in the `Farms`{.action} tab. > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/tcp/farm > -- Details of a specific TCP server: +- Details of a specific TCP server farm: > [!api] > @@ -102,30 +98,30 @@ Your server farm should appear in the list, in the `Farms`{.action} tab. > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/tcp/farm/{farmId} > -## Add a server. +### Add a server -We will now add a server to our server farm. +A server must now be added to the server farm. -### Via the Sunrise Control Panel. +#### Via the OVHcloud Control Panel -In the `Farms`{.action} tab, select the farm you want to add a server to by clicking on the corresponding line. The list of servers already configured in the farm will appear beneath the list of farms, along with the `Add a server`{.action} button. Click on this button to add a new server. +In the `Farms`{.action} tab, select the farm you want to add a server to by clicking on the corresponding line. The list of servers already configured in the farm will appear beneath the list of farms, along with the `Add a server`{.action} button. Click this button to add a new server. -Only the *IPv4 address*, *Status* and *ProxyProtocol version* fields are mandatory. If a server does not use the same port as the one defined earlier in the farm, you may overload it by configuring a server. However, to keep the configuration as standard as possible and easy to maintain, we recommend only using this parameter in advanced cases. +The mandatory fields are the *IPv4 address*, *Status*, and *ProxyProtocol version*. If a server port is configured, it will override the port defined in the farm. To keep the configuration as standard as possible and easy to maintain, we recommend only using this parameter in advanced cases. > [!warning] > -> It is important to configure ProxyProtocol in version v1, so that you can get the real source IP on your SMTP service. Postfix is compatible with this protocol. +> It is important to configure ProxyProtocol in version v1 so that you can retrieve the real source IP on your SMTP service. Postfix is compatible with this protocol. > ![Add a server to a farm.](images/add_server.png){.thumbnail} -Click `Add`{.action} once you have filled in the fields. +Click on `Add`{.action} once you have filled in the fields. Your server should appear in the server list, in the `Farms`{.action} tab, just below the list of farms. ![Details of the server created.](images/resume_server.png){.thumbnail} -### Via the API +#### Via the OVHcloud API - List of servers in the farm: @@ -162,29 +158,29 @@ Your server should appear in the server list, in the `Farms`{.action} tab, just > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/tcp/farm/{farmId}/server > -## Add a front-end +### Add a front-end -We will now add a `front-end`{.action} to our service, and connect it to our server farm. The front-end is the part of your OVH Load Balancer that exposes your service on the internet. +A `front-end`{.action} must now be added to the service and connected to the server farm. The front-end is the component of your OVHcloud Load Balancer that exposes your service to the internet. -### Via the Sunrise Control Panel. +#### Via the OVHcloud Control Panel Go to the `+ Front-ends`{.action} tab, and click `+TCP/TLS`{.action}. -Fill in the fields. The only mandatory fields for a basic configuration are *Port* (25 for a standard SMTP service), *Zone* and *Probe*, if you configured a probe on your farm. If you want your service to be available across several ports at once, you can specify a list of ports, separated by commas, or a range of ports, in the format "start_port-end_port". +Fill in the fields. The mandatory fields for a basic configuration are *Port* (25 for a standard SMTP service), *Zone*, *Default farm* and *Probe* (if a probe was configured on your farm). If you want your service to be available across several ports at once, you can specify a list of ports, separated by commas, or a port range, in the format "-". -If you have routed Additional IPs to your OVH Load Balancer service, you can also attach a front-end to one or more specific Additional IPs. +If you have routed Additional IPs to your OVHcloud Load Balancer service, you can also attach a front-end to one or more specific Additional IPs. -Please remember to specify the farm you created earlier as a “default farm”. +Ensure the farm you created earlier is specified as the “default farm”. ![Add a front-end](images/add_frontend.png){.thumbnail} -Click `Add`{.action} once you have filled in the fields. +Click `Add`{.action} once the fields are filled. Your front-end must appear in the list, in the `Front-ends`{.action} tab. ![Details of the front-end created](images/resume_frontend.png){.thumbnail} -### Via the API +#### Via the OVHcloud API - List of TCP front-ends: @@ -221,17 +217,17 @@ Your front-end must appear in the list, in the `Front-ends`{.action} tab. > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/tcp/frontend/{frontendId} > -## Apply the modifications +### Apply the modifications -The modifications made to your OVH Load Balancer must be *explicitly applied* in each of the zones configured for your service. Only at this point will they be visible to your website visitors. This way, you can make complex configuration changes several times, and only apply them once the configuration is ready. +Modifications made to your OVHcloud Load Balancer must be **explicitly applied** in each of the zones configured for your service. They will only become visible to your users at this point. This process allows for complex configuration changes to be prepared and applied only when fully ready. -If you have several zones, you must apply the same configuration for each of them. +If you have several zones, the same configuration must be applied to each. -### Via the Sunrise Control Panel. +#### Via the OVHcloud Control Panel -Go the homepage for the OVH Load Balancer, and click `Apply:Zone`{.action} for each of the zones concerned. +Go to the homepage for the OVHcloud Load Balancer, and click `Apply:Zone`{.action} for each of the zones concerned. -### Via the API. +#### Via the OVHcloud API - Refresh a zone: @@ -240,21 +236,22 @@ Go the homepage for the OVH Load Balancer, and click `Apply:Zone`{.action} for e > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh > -## Postfix configuration. +### Postfix configuration To make Postfix compatible with HAProxy *ProxyProtocol*, an option is required in the postfix main.cf configuration file: -**smtp_upstream_proxy_protocol = haproxy** +```bash +smtp_upstream_proxy_protocol = haproxy +``` -You then need to restart your Postfix daemon. +The Postfix daemon must then be restarted. -## Confirmation. +### Confirmation -After you have completed all of these steps, you should now have a functional Load Balancer service for your SMTP servers. You can now check the service status by requesting your IP Load Balancer as an SMTP server. +Upon completing these steps, you will have a functional Load Balancer service for your SMTP servers. The service status can now be checked by requesting your IP Load Balancer as an SMTP server. ![Connection to SMTP via telnet](images/resume_validate.png){.thumbnail} ## Go further -Join our community of users on . - +Join our [community of users](/links/community). diff --git a/pages/network/load_balancer/case_smtp/guide.en-us.md b/pages/network/load_balancer/case_smtp/guide.en-us.md index 81712ab5352..6ff6bd90aa2 100644 --- a/pages/network/load_balancer/case_smtp/guide.en-us.md +++ b/pages/network/load_balancer/case_smtp/guide.en-us.md @@ -1,71 +1,67 @@ --- -title: 'Configuring SMTP on a Load Balancer service' -excerpt: 'Find out how to use SMTP with the OVH Load Balancer' -updated: 2018-12-28 +title: 'How to configure SMTP on a Load Balancer service' +excerpt: 'Find out how to use SMTP with the OVHcloud Load Balancer' +updated: 2025-10-24 --- ## Objective -In this guide, we will configure a basic TCP load balancing service, for one or more SMTP servers. A TCP front-end will listen to TCP traffic on port 25. It is configured to direct traffic to a TCP farm with one or more TCP servers, depending on how you choose to configure it. +**This guide outlines how to configure the OVHcloud Load Balancer to distribute traffic across multiple SMTP servers.** -**This guide is designed to help you configure an OVH Load Balancer service in order to balance load across several servers that respond in SMTP.** +## Requirements -> [!warning] -> -> Questions on what an SMTP service is and how it works will not be covered here. This guide is aimed at readers who have a general understanding of SMTP, or practical experience with it. -> +- An [OVHcloud Load balancer](/links/network/load-balancer) service in your OVHcloud account. +- Access to the [OVHcloud Control Panel](/links/manager). +- A Postfix-type SMTP service installed and configured on your servers. -> [!warning] -> -> We will assume that you already have a Postfix SMTP service set up and configured your servers. -> +## Instructions > [!warning] > -> This guide will take you through the steps required. Depending on the way you have designed your architecture, some configurations may vary. +> This guide assumes a working knowledge of SMTP protocol and service operation. > -As a reminder, each protocol (HTTP, TCP and UDP) in the OVH Load Balancer service has its own associated front-ends, farms and servers. +As a reminder, each protocol (HTTP, TCP and UDP) in the OVHcloud Load Balancer service has its own associated front-ends, farms and servers. > [!warning] > -> The order in which elements are created is important. In particular, the server farms must be configured before we can attach servers to them. +> The order in which elements are created is important. In particular, the server farms must be configured before servers can be attached to them. > -In the Sunrise Control Panel, you will see the features detailed below: +In the Control Panel, you will see the features detailed below: -![OVH Load Balancer service](images/iplb_service.png){.thumbnail} +![OVHcloud Load Balancer service](images/iplb_service.png){.thumbnail} -Via the OVH API, in the section: +Via the OVHcloud API, use the following call: > [!api] > > @api {v1} /ipLoadbalancing GET /ipLoadbalancing > -For more information on the API’s features, you can refer to the following guide: [Load Balancer API Quick Reference](/pages/network/load_balancer/use_api_reference){.ref} +For more information on the API features, you can refer to [the following guide](/pages/network/load_balancer/use_api_reference). -## Add a server farm. +### Add a server farm -We will add a farm of TCP servers to our service, which is the part that balances traffic on the servers. +A TCP server farm must be added to the service; this component manages traffic balancing across the servers. -### Via the Sunrise Control Panel. +#### Via the OVHcloud Control Panel In the `Farms`{.action} tab for servers, click on the `+TCP/TLS`{.action} button. -Fill in the fields. The mandatory fields for a basic configuration are *Port* and *Zone*. In our case, for SMTP, port 25 is used. If no ports are specified, your OVH Load Balancer will automatically use the same port as the corresponding front-end. +Fill in the fields. The mandatory fields for a basic configuration are *Port* and *Zone*. For SMTP, port 25 is used. If no ports are specified, your OVHcloud Load Balancer will automatically use the same port as the corresponding front-end. -As an option, you can add an SMTP probe on your farm. +Optionally, you can add an SMTP probe on your farm. ![Add a server farm via the Control Panel](images/add_farm.png){.thumbnail} -Click `Add`{.action} once you have filled in the fields. +Click on `Add`{.action} once you have filled in the fields. Your server farm should appear in the list, in the `Farms`{.action} tab. ![Details of the server farm created](images/resume_farm.png){.thumbnail} -### Via the API +#### Via the OVHcloud API - List of TCP server farms: @@ -74,7 +70,7 @@ Your server farm should appear in the list, in the `Farms`{.action} tab. > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/tcp/farm > -- Details of a specific TCP server: +- Details of a specific TCP server farm: > [!api] > @@ -102,30 +98,30 @@ Your server farm should appear in the list, in the `Farms`{.action} tab. > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/tcp/farm/{farmId} > -## Add a server. +### Add a server -We will now add a server to our server farm. +A server must now be added to the server farm. -### Via the Sunrise Control Panel. +#### Via the OVHcloud Control Panel -In the `Farms`{.action} tab, select the farm you want to add a server to by clicking on the corresponding line. The list of servers already configured in the farm will appear beneath the list of farms, along with the `Add a server`{.action} button. Click on this button to add a new server. +In the `Farms`{.action} tab, select the farm you want to add a server to by clicking on the corresponding line. The list of servers already configured in the farm will appear beneath the list of farms, along with the `Add a server`{.action} button. Click this button to add a new server. -Only the *IPv4 address*, *Status* and *ProxyProtocol version* fields are mandatory. If a server does not use the same port as the one defined earlier in the farm, you may overload it by configuring a server. However, to keep the configuration as standard as possible and easy to maintain, we recommend only using this parameter in advanced cases. +The mandatory fields are the *IPv4 address*, *Status*, and *ProxyProtocol version*. If a server port is configured, it will override the port defined in the farm. To keep the configuration as standard as possible and easy to maintain, we recommend only using this parameter in advanced cases. > [!warning] > -> It is important to configure ProxyProtocol in version v1, so that you can get the real source IP on your SMTP service. Postfix is compatible with this protocol. +> It is important to configure ProxyProtocol in version v1 so that you can retrieve the real source IP on your SMTP service. Postfix is compatible with this protocol. > ![Add a server to a farm.](images/add_server.png){.thumbnail} -Click `Add`{.action} once you have filled in the fields. +Click on `Add`{.action} once you have filled in the fields. Your server should appear in the server list, in the `Farms`{.action} tab, just below the list of farms. ![Details of the server created.](images/resume_server.png){.thumbnail} -### Via the API +#### Via the OVHcloud API - List of servers in the farm: @@ -162,29 +158,29 @@ Your server should appear in the server list, in the `Farms`{.action} tab, just > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/tcp/farm/{farmId}/server > -## Add a front-end +### Add a front-end -We will now add a `front-end`{.action} to our service, and connect it to our server farm. The front-end is the part of your OVH Load Balancer that exposes your service on the internet. +A `front-end`{.action} must now be added to the service and connected to the server farm. The front-end is the component of your OVHcloud Load Balancer that exposes your service to the internet. -### Via the Sunrise Control Panel. +#### Via the OVHcloud Control Panel Go to the `+ Front-ends`{.action} tab, and click `+TCP/TLS`{.action}. -Fill in the fields. The only mandatory fields for a basic configuration are *Port* (25 for a standard SMTP service), *Zone* and *Probe*, if you configured a probe on your farm. If you want your service to be available across several ports at once, you can specify a list of ports, separated by commas, or a range of ports, in the format "start_port-end_port". +Fill in the fields. The mandatory fields for a basic configuration are *Port* (25 for a standard SMTP service), *Zone*, *Default farm* and *Probe* (if a probe was configured on your farm). If you want your service to be available across several ports at once, you can specify a list of ports, separated by commas, or a port range, in the format "-". -If you have routed Additional IPs to your OVH Load Balancer service, you can also attach a front-end to one or more specific Additional IPs. +If you have routed Additional IPs to your OVHcloud Load Balancer service, you can also attach a front-end to one or more specific Additional IPs. -Please remember to specify the farm you created earlier as a “default farm”. +Ensure the farm you created earlier is specified as the “default farm”. ![Add a front-end](images/add_frontend.png){.thumbnail} -Click `Add`{.action} once you have filled in the fields. +Click `Add`{.action} once the fields are filled. Your front-end must appear in the list, in the `Front-ends`{.action} tab. ![Details of the front-end created](images/resume_frontend.png){.thumbnail} -### Via the API +#### Via the OVHcloud API - List of TCP front-ends: @@ -221,17 +217,17 @@ Your front-end must appear in the list, in the `Front-ends`{.action} tab. > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/tcp/frontend/{frontendId} > -## Apply the modifications +### Apply the modifications -The modifications made to your OVH Load Balancer must be *explicitly applied* in each of the zones configured for your service. Only at this point will they be visible to your website visitors. This way, you can make complex configuration changes several times, and only apply them once the configuration is ready. +Modifications made to your OVHcloud Load Balancer must be **explicitly applied** in each of the zones configured for your service. They will only become visible to your users at this point. This process allows for complex configuration changes to be prepared and applied only when fully ready. -If you have several zones, you must apply the same configuration for each of them. +If you have several zones, the same configuration must be applied to each. -### Via the Sunrise Control Panel. +#### Via the OVHcloud Control Panel -Go the homepage for the OVH Load Balancer, and click `Apply:Zone`{.action} for each of the zones concerned. +Go to the homepage for the OVHcloud Load Balancer, and click `Apply:Zone`{.action} for each of the zones concerned. -### Via the API. +#### Via the OVHcloud API - Refresh a zone: @@ -240,21 +236,22 @@ Go the homepage for the OVH Load Balancer, and click `Apply:Zone`{.action} for e > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh > -## Postfix configuration. +### Postfix configuration To make Postfix compatible with HAProxy *ProxyProtocol*, an option is required in the postfix main.cf configuration file: -**smtp_upstream_proxy_protocol = haproxy** +```bash +smtp_upstream_proxy_protocol = haproxy +``` -You then need to restart your Postfix daemon. +The Postfix daemon must then be restarted. -## Confirmation. +### Confirmation -After you have completed all of these steps, you should now have a functional Load Balancer service for your SMTP servers. You can now check the service status by requesting your IP Load Balancer as an SMTP server. +Upon completing these steps, you will have a functional Load Balancer service for your SMTP servers. The service status can now be checked by requesting your IP Load Balancer as an SMTP server. ![Connection to SMTP via telnet](images/resume_validate.png){.thumbnail} ## Go further -Join our community of users on . - +Join our [community of users](/links/community). diff --git a/pages/network/load_balancer/case_smtp/guide.fr-ca.md b/pages/network/load_balancer/case_smtp/guide.fr-ca.md index 243a9fee82c..76651178f56 100644 --- a/pages/network/load_balancer/case_smtp/guide.fr-ca.md +++ b/pages/network/load_balancer/case_smtp/guide.fr-ca.md @@ -1,241 +1,241 @@ --- -title: 'Configurer SMTP sur un service Load Balancer' -excerpt: 'Cas pratique SMTP' -updated: 2018-12-28 +title: 'Comment configurer le SMTP sur un service Load Balancer' +excerpt: 'Découvrez comment utiliser le SMTP avec le Load Balancer OVHcloud' +updated: 2025-10-24 --- -## Introduction -Ce guide a pour but de vous aider à configurer un service OVH Load Balancer OVH pour répartir la charge sur plusieurs serveurs répondant convenablement en SMTP. +## Objectif -> [!warning] -> -> Les questions de ce qu'est un service SMTP, et son fonctionnement, ne seront pas abordées ici. -> Il est considéré que ces informations sont raisonnablement comprises et/ou maîtrisées. -> +**Ce guide détaille la configuration du Load Balancer OVHcloud afin de distribuer le trafic entre plusieurs serveurs SMTP.** -> [!warning] -> -> Nous considérons que vous avez déjà un service SMTP de type postfix installé et configuré sur vos serveurs. -> +## Prérequis + +- Posséder une offre [OVHcloud Load balancer](/links/network/load-balancer) dans votre compte OVHcloud. +- Être connecté à votre [espace client OVHcloud](/links/manager). +- Posséder un service SMTP de type Postfix installé et configuré sur vos serveurs. + +## En pratique > [!warning] > -> Nous allons vous guider au travers des différentes étapes. -> Dépendant de vos choix d'architecture, certaines configurations peuvent différer. -> +> Ce guide présuppose une connaissance fonctionnelle du protocole SMTP et de son service. +> -Dans ce guide, nous allons configurer un service simple de Load Balancing TCP, pour un (ou plusieurs) serveur(s) SMTP. Un Frontend TCP écoutera le trafic TCP sur le port 25. Il sera configuré pour diriger le trafic sur une Ferme TCP, avec un ou plusieurs Serveurs TCP, selon votre configuration. +Dans ce guide, nous configurons un service simple d'équilibrage de charge TCP pour un (ou plusieurs) serveur(s) SMTP. Un *frontend* TCP écoutera le trafic TCP sur le port 25. Il sera configuré pour diriger le trafic vers une ferme TCP, comprenant un ou plusieurs serveurs TCP, selon la configuration retenue. -Pour rappel, chaque protocole (HTTP, TCP et UDP) dans le service OVH Load Balancer dispose de ses propres Frontends, Fermes et Serveurs associés. +Pour rappel, chaque protocole (HTTP, TCP et UDP) du service OVHcloud Load Balancer dispose de ses propres *frontends*, fermes et serveurs associés. > [!warning] > > L'ordre de création des éléments est important. -> En particulier, les Fermes de serveurs doivent être configurées avant de pouvoir leur attacher des Serveurs. -> +> En particulier, les fermes de serveurs doivent être configurées **avant** de pouvoir leur attacher des serveurs. +> -Dans le Manager nous allons retrouver les fonctionnalités détaillées ci-dessous : +Les fonctionnalités détaillées ci-dessous sont disponibles dans l'espace client OVHcloud : -![Service OVH Load Balancer](images/iplb_service.png){.thumbnail} +![Service OVHcloud Load Balancer](images/iplb_service.png){.thumbnail} -Via l'API OVH, dans la section +Depuis l'API OVHcloud : > [!api] > > @api {v1} /ipLoadbalancing GET /ipLoadbalancing > -Pour plus d'informations sur les fonctionnalités de l'API, consulter la page [Référence Rapide API Load Balancer](/pages/network/load_balancer/use_api_reference){.ref}. +Pour plus d'informations sur les fonctionnalités de l'API, consultez la page « [Détails des fonctions API](/pages/network/load_balancer/use_api_details) ». -## Ajouter une `Ferme`{.action} de serveurs +### Ajouter une ferme de serveurs -Nous allons ajouter une Ferme de serveurs TCP à notre service, la partie en charge de répartir le trafic sur les serveurs. +Une ferme de serveurs TCP doit être ajoutée à notre service ; ce composant est en charge de la répartition du trafic sur les serveurs. -### Via le Manager +#### Depuis l'espace client OVHcloud Dans l'onglet `Fermes`{.action} de serveurs, cliquez sur le bouton `+TCP/TLS`{.action}. -Remplissez les différents champs. Les champs obligatoires pour une configuration simple sont le *Port* et la *Zone*. Dans notre cas, pour SMTP, le port utilisé est le port 25. Si aucun port n'est spécifié, votre OVH Load Balancer utilisera automatiquement le même port que le Frontend correspondant. +Remplissez les différents champs. Les champs obligatoires pour une configuration simple sont le *Port* et la *Zone*. Dans notre cas, pour SMTP, le port utilisé est le port 25. Si aucun port n'est spécifié, votre OVHcloud Load Balancer utilisera automatiquement le même port que le *frontend* correspondant. -Vous pouvez optionnelement ajouter une sonde de type smtp sur votre Ferme. +Vous pouvez optionnelement ajouter une sonde de type SMTP sur votre ferme. ![Ajout d'une ferme de serveurs via le Manager](images/add_farm.png){.thumbnail} +![Ajout d'une ferme de serveurs via le Manager](images/add_farm_Probe.png){.thumbnail} + Cliquez sur le bouton `Ajouter`{.action} une fois les champs remplis. -Votre Ferme de serveurs devrait apparaître dans la liste, sous l'onglet `Fermes`{.action}. +Votre ferme de serveurs devrait apparaître dans la liste, sous l'onglet `Fermes`{.action}. ![Détails de la ferme de serveurs créée](images/resume_farm.png){.thumbnail} -### Via l'API +#### Depuis l'API OVHcloud -- Liste des Fermes de serveurs TCP : +- Liste des fermes de serveurs TCP : > [!api] > > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/tcp/farm > -- Détails d'un serveur TCP spécifique : +- Détails d'une ferme de serveurs TCP : > [!api] > > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/tcp/farm/{farmId} > -- Ajout d'une nouvelle Ferme de serveurs TCP : +- Ajout d'une nouvelle ferme de serveurs TCP : > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/tcp/farm > -- Modification d'une Ferme de serveurs spécifique : +- Modification d'une ferme de serveurs spécifique : > [!api] > > @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/tcp/farm/{farmId} > -- Suppression d'une Ferme de serveurs spécifique : +- Suppression d'une ferme de serveurs spécifique : > [!api] > > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/tcp/farm/{farmId} > -## Ajouter un `Serveur`{.action} +### Ajouter un serveur -Nous allons maintenant ajouter un serveur à notre Ferme de serveurs. +Un serveur doit maintenant être ajouté à la ferme de serveurs. -### Via le Manager +#### Depuis l'espace client OVHcloud -Toujours dans l'onglet `Ferme`{.action}, sélectionnez la Ferme dans laquelle vous souhaitez ajouter un serveur en cliquant sur la ligne correspondante. La liste des Serveurs déjà configurés dans la Ferme apparaît en dessous de la liste des Fermes, ainsi qu'un bouton `+Server`{.action}. Cliquez sur ce bouton pour ajouter un nouveau serveur. +Toujours dans l'onglet `Fermes`{.action}, sélectionnez la ferme dans laquelle vous souhaitez ajouter un serveur en cliquant sur la ligne correspondante. La liste des serveurs déjà configurés dans la ferme apparaît en dessous de la liste des fermes, ainsi qu'un bouton `+Server`{.action}. Cliquez sur ce bouton pour ajouter un nouveau serveur. -Seuls les champs *Adresse IPv4*, *État* et *Version du ProxyProtocol* sont obligatoires. Si un serveur n'utilise pas le même port que celui défini plus haut dans la Ferme, il est possible de le surcharger dans la configuration du serveur. Cependant, afin de conserver une configuration la plus homogène et maintenable possible, il est recommandé de n'utiliser ce paramètre que dans les cas avancés. +Les champs obligatoires sont l'*Adresse IPv4*, l'*État* et la *Version du ProxyProtocol*. Si un port de serveur est configuré, il remplacera le port défini au niveau de la ferme. Afin de conserver une configuration la plus homogène et maintenable possible, il est recommandé de n'utiliser ce paramètre que dans les cas avancés. > [!warning] > -> Il est important de configurer le ProxyProtocol en version v1, -> afin d'obtenir l'IP source réelle sur votre service SMTP. +> Il est important de configurer le ProxyProtocol en version v1 afin d'obtenir l'IP source réelle sur votre service SMTP. > Postfix est compatible avec ce protocole. > -![Ajour d'un serveur dans une Ferme.](images/add_server.png){.thumbnail} +![Ajout d'un serveur dans une ferme](images/add_server.png){.thumbnail} + +![Ajout d'un serveur dans une ferme](images/add_server_advance.png){.thumbnail} Cliquez sur le bouton `Ajouter`{.action} une fois les champs remplis. -Votre Serveur devrait apparaître dans la liste des Serveurs l'onglet `Fermes`{.action}, juste en dessous de la liste des Fermes. +Votre serveur devrait apparaître dans la liste des serveurs dans l'onglet `Fermes`{.action}, juste en dessous de la liste des fermes. -![Détails du serveur créé.](images/resume_server.png){.thumbnail} +![Détails du serveur créé](images/resume_server.png){.thumbnail} -### Via l'API +### Depuis l'API OVHcloud -- Liste des Serveurs de la Ferme : +- Liste des serveurs de la ferme : > [!api] > > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/tcp/farm/{farmId}/server > -- Détails d'un Serveur spécifique : +- Détails d'un serveur spécifique : > [!api] > > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/tcp/farm/{farmId}/server/{serverId} > -- Ajout d'un nouveau Serveur : +- Ajout d'un nouveau serveur : > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/tcp/farm/{farmId}/server > -- Modification d'un Serveur spécifique : +- Modification d'un serveur spécifique : > [!api] > > @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/tcp/farm/{farmId}/server > -- Suppression d'un Serveur spécifique : +- Suppression d'un serveur spécifique : > [!api] > > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/tcp/farm/{farmId}/server > -## Ajouter un `Frontend`{.action} +### Ajouter un frontend -Nous allons maintenant ajouter un `Frontend`{.action} à notre service et le connecter à notre Ferme de serveurs. Le Frontend est la partie de votre OVH Load Balancer qui sert à exposer votre service sur Internet. +Un *frontend* doit maintenant être ajouté à notre service et connecté à la ferme de serveurs. Le *frontend* est le composant de votre OVHcloud Load Balancer qui expose votre service sur Internet. -### Via le Manager +#### Depuis l'espace client OVHcloud Dans l'onglet `+Frontends`{.action}, cliquez sur le bouton `+TCP/TLS`{.action}. -Remplissez les différents champs. Les seuls champs obligatoires pour une configuration simple sont le *Port* (25 pour un service SMTP standard), la *Zone* et la *Sonde* si vous en avez configuré un dans votre Ferme. Si vous souhaitez que votre service soit disponible sur plusieurs ports en même temps, vous pouvez spécifier une liste de ports séparés par des virgules ou une plage de ports de la forme "-". +Remplissez les différents champs. Les seuls champs obligatoires pour une configuration simple sont le *Port* (25 pour un service SMTP standard), la *Zone*, la *Ferme par défaut* et la *Sonde* (si vous en avez configuré une dans votre Ferme). Si vous souhaitez que votre service soit disponible sur plusieurs ports en même temps, vous pouvez spécifier une liste de ports séparés par des virgules ou une plage de ports de la forme "-". -Si vous avez routé des Additional IPs vers votre service OVH Load Balancer, vous pouvez également attacher un Frontend à une ou plusieurs Additional IPs spécifiques. +Si vous avez routé des Additional IP vers votre service OVHcloud Load Balancer, vous pouvez également attacher un *frontend* à une ou plusieurs Additional IP spécifiques. -N'oubliez pas de spécifier comme «Ferme par défaut» la Ferme créée précédemment. +Assurez-vous de spécifier la ferme créée précédemment comme « Ferme par défaut ». ![Ajout d'un frontend](images/add_frontend.png){.thumbnail} Cliquez sur le bouton `Ajouter`{.action} une fois les champs remplis. -Votre Frontend devrait apparaître dans la liste, sous l'onglet `Frontends`{.action}. +Votre *frontend* devrait apparaître dans la liste, sous l'onglet `Frontends`{.action}. ![Détails du frontend créé](images/resume_frontend.png){.thumbnail} -### Via l'API +#### Depuis l'API OVHcloud -- Liste des Frontends TCP : +- Liste des *frontends* TCP : > [!api] > > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/tcp/frontend > -- Détails d'un Frontend spécifique : +- Détails d'un *frontend* spécifique : > [!api] > > @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/tcp/frontend/{frontendId} > -- Ajout d'un nouveau Frontend : +- Ajout d'un nouveau *frontend* : > [!api] > > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/tcp/frontend > -- Modification d'un Frontend spécifique : +- Modification d'un *frontend* spécifique : > [!api] > > @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/tcp/frontend/{frontendId} > -- Suppression d'un Frontend spécifique : +- Suppression d'un *frontend* spécifique : > [!api] > > @api {v1} /ipLoadbalancing DELETE /ipLoadbalancing/{serviceName}/tcp/frontend/{frontendId} > -## Appliquer les modifications +### Appliquer les modifications -Les modifications apportées à votre service OVH Load Balancer doivent être *appliquées explicitement* dans chacune des zones configurées pour votre service OVH Load Balancer. C'est seulement à ce moment qu'elles seront visibles pour vos visiteurs. Cela permet de faire un changement complexe de configuration en plusieurs fois, et de ne l'appliquer que lorsque la configuration est prête. +Les modifications apportées à votre service OVHcloud Load Balancer doivent être **appliquées explicitement** dans chacune des zones configurées pour votre service. C'est seulement à ce moment qu'elles deviendront visibles pour vos visiteurs. Ce processus permet de préparer des changements de configuration complexes et de ne les appliquer qu'une fois la configuration entièrement prête. -Si vous avez plusieurs zones, vous devrez appliquer la même configuration pour chacune de vos zones. +Si vous avez plusieurs zones, la même configuration devra être appliquée pour chacune de vos zones. -### Via le Manager +#### Depuis l'espace client OVHcloud -Rendez-vous sur la page principale de votre service OVH Load Balancer et cliquez sur les boutons `Appliquer:Zone`{.action} pour chacune des zones concernées. +Rendez-vous sur la page principale de votre service OVHcloud Load Balancer et cliquez sur les boutons `Appliquer:Zone`{.action} pour chacune des zones concernées. -### Via l'API +#### Depuis l'API OVHcloud - Rafraîchir une zone : @@ -244,16 +244,22 @@ Rendez-vous sur la page principale de votre service OVH Load Balancer et cliquez > @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh > -## Configuration de postfix +### Configuration de Postfix -Afin de rendre compatible postfix avec le *ProxyProtocol* de haproxy, une option est requise dans le fichier de configuration postfix main.cf. +Afin de rendre Postfix compatible avec le *ProxyProtocol* de HAProxy, une option est requise dans le fichier de configuration `postfix main.cf` : +```bash smtp_upstream_proxy_protocol = haproxy +``` -Vous devez ensuite redémarrer votre démon postfix. +Le daemon Postfix doit ensuite être redémarré. -## Validation +### Validation Une fois toutes ces étapes terminées, vous devriez disposer d'un service de répartition de charge fonctionnel pour vos serveurs SMTP. Vous pouvez alors valider l'état du service en interrogeant votre IPLB comme un serveur SMTP. ![Connexion à SMTP via telnet](images/resume_validate.png){.thumbnail} + +## Aller plus loin + +Échangez avec notre [communauté d'utilisateurs](/links/community). diff --git a/pages/network/load_balancer/case_smtp/guide.fr-fr.md b/pages/network/load_balancer/case_smtp/guide.fr-fr.md index 51a449da24e..76651178f56 100644 --- a/pages/network/load_balancer/case_smtp/guide.fr-fr.md +++ b/pages/network/load_balancer/case_smtp/guide.fr-fr.md @@ -1,7 +1,7 @@ --- title: 'Comment configurer le SMTP sur un service Load Balancer' excerpt: 'Découvrez comment utiliser le SMTP avec le Load Balancer OVHcloud' -updated: 2025-10-21 +updated: 2025-10-24 --- ## Objectif diff --git a/pages/network/load_balancer/create_balancing/guide.de-de.md b/pages/network/load_balancer/create_balancing/guide.de-de.md deleted file mode 100644 index 3b904017b58..00000000000 --- a/pages/network/load_balancer/create_balancing/guide.de-de.md +++ /dev/null @@ -1,105 +0,0 @@ ---- -title: Lastverteilungstyp -excerpt: Diese Anleitung beschreibt die verschiedenen Lastverteilungsmethoden des OVH Loadbalancers -updated: 2018-01-17 ---- - -## Einleitung - -Der neue OVH Loadbalancer bietet Ihnen mehrere Lastverteilungstypen für Ihre Dienste. Die gewählte Methode bestimmt, wie der OVH Loadbalancer die empfangenen Anfragen auf Ihre Server aufteilt. - -**Diese Anleitung gibt eine Einführung zu den verschiedenen Lastverteilungstypen und zeigt Ihnen, wie Sie diese ändern können.** - -## Voraussetzungen - -- Sie sind in Ihrem [OVHcloud Kundencenter](/links/manager) eingeloggt. -- Sie haben eine Serverfarm erstellt. - -## Beschreibung - -### Die verschiedenen Lastverteilungstypen - -Lastverteilung (engl. „Load Balancing“) wird in Serverfarmen verwendet. Diese Einstellung bestimmt, wie Anfragen zwischen den verschiedenen Servern einer Farm aufgeteilt werden. - -Weitere Informationen zu den Grundbestandteilen des OVH Loadbalancers finden Sie in der [Einführung zum OVH Loadbalancer](/pages/network/load_balancer/use_presentation). - -|Algorithmus|Funktion| -|---|---| -|First|Der erste verfügbare Server empfängt die Verbindung. Der Server wird entsprechend seiner ID ausgewählt, immer von der kleinsten zur größten.| -|LeastConn|Wählt den Server mit den wenigsten aktiven Verbindungen aus. Diese Einstellung wird für längere Sitzungen mit geringem Traffic empfohlen. Der *RoundRobin* Algorithmus wird auf Gruppen von Servern mit gleicher Anzahl an Verbindungen angewendet.| -|RoundRobin|Wählt einen Server nach dem anderen für jede Verbindung. **Dieser Algorithmus ist standardmäßig eingestellt.**| -|Source|Dieser Algorithmus wendet eine *Hashfunktion* auf die Quell-IP an und teilt anschließend das Ergebnis durch die Anzahl der aktuell aktiven Server. So wird die gleiche Quell-IP immer auf denselben Server weitergeleitet, solange dieser aktiv ist.| -|URI|Dieser Algorithmus wendet eine *Hashfunktion* auf einen Teil oder den kompletten URI an und teilt anschließend das Ergebnis durch die Anzahl der aktuell aktiven Server. So wird der gleiche URI immer auf denselben Server weitergeleitet, solange dieser aktiv ist.| - -### Lastverteilungstyp einer Farm über das Kundencenter anpassen - -- Im Bereich `Serverfarmen`{.action} Ihres OVH Loadbalancers werden Ihnen die aktuell eingerichteten Serverfarmen angezeigt. Um eine der Farmen zu bearbeiten, klicken Sie einfach auf die drei Punkte rechts neben der entsprechenden Farm (2) und anschließend auf `Ändern`{.action}: - -![Serverfarm bearbeiten](images/server_cluster_change.png){.thumbnail} - -In den `erweiterten Einstellungen`{.action} können Sie Ihren `Lastverteilungstyp`{.action} ändern: - -![Serverfarm bearbeiten](images/distrib_mode_edit.png){.thumbnail} - -Wenn Sie den gewünschten Lastverteilungstyp ausgewählt haben, klicken Sie auf `Update`{.action} und dann auf `Die Konfiguration anwenden`{.action} in dem angezeigten gelben Banner: - -![Konfiguration anwenden](images/apply_config.png){.thumbnail} - -### Lastverteilungstyp einer Farm über die API anpassen - -Sie können die Einstellungen des Lastverteilungstyps anpassen, indem Sie die entsprechenden Einstellungen in den Serverfarmen vornehmen. - -- Details einer Farm einsehen - -Mit dieser API-Funktion können Sie sich die Details einer Farm anzeigen lassen, wenn Sie deren ID kennen. Im folgenden Beispiel werden wir eine HTTP-Farm bearbeiten: - -> [!api] -> -> @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/http/farm/{farmId} -> - -|Einstellung|Bedeutung| -|---|---| -|ServiceName*|ID Ihres Loadbalancer Dienstes| -|farmId*|ID der Farm| - -|Antwort (BackendHttp)|Bedeutung| -|---|---| -|farmId|ID der Farm| -|balance|Aktuell auf der Farm konfigurierter Lastverteilungstyp| -|zone|Name der Zone, in der die Farm konfiguriert ist| -|port|Port, der verwendet wird, um die Server zu kontaktieren| -|probe|Aktuell auf der Farm konfigurierte Monitoring-Sonde| -|displayName|Name der Farm| -|stickiness|Aktuell auf der Farm konfigurierte Verbindungsüberwachung| - -- Lastverteilungstyp anpassen - -Mit diesem Aufrufbefehl können Sie die Konfiguration einer Farm bearbeiten, wenn Sie deren ID kennen. Im folgenden Beispiel werden wir eine HTTP-Farm bearbeiten. Um den Lastverteilungstyp zu ändern, aktualisieren Sie das Feld `BackendHttp.balance` mit einem verfügbaren Lastverteilungstyp: - -> [!api] -> -> @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/http/farm/{id} -> - -|Einstellung|Bedeutung| -|---|---| -|ServiceName*|ID Ihres Loadbalancer Dienstes| -|farmId*|ID der Farm| -|BackendHttp.balance|Der gewünschte Lastverteilungstyp für diese Farm| - -- Änderungen anwenden - -> [!api] -> -> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh -> - -|Einstellung|Bedeutung| -|---|---| -|ServiceName*|ID Ihres Loadbalancer Dienstes| -|zone*|Name der Zone, in der die Konfiguration angewendet werden soll| - -## Weiterführende Informationen - -Für den Austausch mit unserer User Community gehen Sie auf . diff --git a/pages/network/load_balancer/create_balancing/guide.en-asia.md b/pages/network/load_balancer/create_balancing/guide.en-asia.md index 6236c3c22f6..ddb51f2c8cf 100644 --- a/pages/network/load_balancer/create_balancing/guide.en-asia.md +++ b/pages/network/load_balancer/create_balancing/guide.en-asia.md @@ -1,7 +1,7 @@ --- title: Load balancing methods excerpt: Discover the various load balancing algorithms available with the OVHcloud Load Balancer -updated: 2025-10-23 +updated: 2025-10-24 --- ## Objective diff --git a/pages/network/load_balancer/create_balancing/guide.en-au.md b/pages/network/load_balancer/create_balancing/guide.en-au.md index 6236c3c22f6..ddb51f2c8cf 100644 --- a/pages/network/load_balancer/create_balancing/guide.en-au.md +++ b/pages/network/load_balancer/create_balancing/guide.en-au.md @@ -1,7 +1,7 @@ --- title: Load balancing methods excerpt: Discover the various load balancing algorithms available with the OVHcloud Load Balancer -updated: 2025-10-23 +updated: 2025-10-24 --- ## Objective diff --git a/pages/network/load_balancer/create_balancing/guide.en-ca.md b/pages/network/load_balancer/create_balancing/guide.en-ca.md index 6236c3c22f6..ddb51f2c8cf 100644 --- a/pages/network/load_balancer/create_balancing/guide.en-ca.md +++ b/pages/network/load_balancer/create_balancing/guide.en-ca.md @@ -1,7 +1,7 @@ --- title: Load balancing methods excerpt: Discover the various load balancing algorithms available with the OVHcloud Load Balancer -updated: 2025-10-23 +updated: 2025-10-24 --- ## Objective diff --git a/pages/network/load_balancer/create_balancing/guide.en-gb.md b/pages/network/load_balancer/create_balancing/guide.en-gb.md index 6236c3c22f6..ddb51f2c8cf 100644 --- a/pages/network/load_balancer/create_balancing/guide.en-gb.md +++ b/pages/network/load_balancer/create_balancing/guide.en-gb.md @@ -1,7 +1,7 @@ --- title: Load balancing methods excerpt: Discover the various load balancing algorithms available with the OVHcloud Load Balancer -updated: 2025-10-23 +updated: 2025-10-24 --- ## Objective diff --git a/pages/network/load_balancer/create_balancing/guide.en-ie.md b/pages/network/load_balancer/create_balancing/guide.en-ie.md index 6236c3c22f6..ddb51f2c8cf 100644 --- a/pages/network/load_balancer/create_balancing/guide.en-ie.md +++ b/pages/network/load_balancer/create_balancing/guide.en-ie.md @@ -1,7 +1,7 @@ --- title: Load balancing methods excerpt: Discover the various load balancing algorithms available with the OVHcloud Load Balancer -updated: 2025-10-23 +updated: 2025-10-24 --- ## Objective diff --git a/pages/network/load_balancer/create_balancing/guide.en-sg.md b/pages/network/load_balancer/create_balancing/guide.en-sg.md index 6236c3c22f6..ddb51f2c8cf 100644 --- a/pages/network/load_balancer/create_balancing/guide.en-sg.md +++ b/pages/network/load_balancer/create_balancing/guide.en-sg.md @@ -1,7 +1,7 @@ --- title: Load balancing methods excerpt: Discover the various load balancing algorithms available with the OVHcloud Load Balancer -updated: 2025-10-23 +updated: 2025-10-24 --- ## Objective diff --git a/pages/network/load_balancer/create_balancing/guide.en-us.md b/pages/network/load_balancer/create_balancing/guide.en-us.md index 6236c3c22f6..ddb51f2c8cf 100644 --- a/pages/network/load_balancer/create_balancing/guide.en-us.md +++ b/pages/network/load_balancer/create_balancing/guide.en-us.md @@ -1,7 +1,7 @@ --- title: Load balancing methods excerpt: Discover the various load balancing algorithms available with the OVHcloud Load Balancer -updated: 2025-10-23 +updated: 2025-10-24 --- ## Objective diff --git a/pages/network/load_balancer/create_balancing/guide.es-es.md b/pages/network/load_balancer/create_balancing/guide.es-es.md deleted file mode 100644 index a8e597376be..00000000000 --- a/pages/network/load_balancer/create_balancing/guide.es-es.md +++ /dev/null @@ -1,107 +0,0 @@ ---- -title: 'Modos de balanceo' -excerpt: 'Modos de balanceo de la carga del Load Balancer de OVH' -updated: 2018-01-17 ---- - -## Objetivo - -El nuevo Load Balancer de OVH ofrece distintos tipos de balanceo de la carga de los servicios, que determinan la forma en la que las peticiones recibidas se distribuyen entre los servidores. - -**Esta guía explica los distintos tipos de balanceo de carga y cómo cambiar entre ellos.** - -## Requisitos - -- Estar conectado al [área de cliente de OVH](/links/manager). -- Haber creado una granja de servidores. - -## Procedimiento - -### Tipos de balanceo de la carga - -En las granjas de servidores, el balanceo de carga determina la forma en la que las peticiones se distribuirán entre los distintos servidores de la granja. - -Para conocer las principales características del Load Balancer de OVH, consulte la [guía de presentación del servicio](/pages/network/load_balancer/use_presentation). - -|Algoritmo|Funcionalidades| -|---|---| -|Round-robin|Elige un servidor tras otro en cada conexión. Es el algoritmo utilizado por defecto.| -|First|El primer servidor disponible recibe la conexión. El orden de los servidores se elige en función de su ID, de menor a mayor.| -|Least|Elige el servidor con menos conexiones activas. Se recomienda elegir este algoritmo para sesiones prolongadas con poco tráfico. En los grupos de servidores que tienen el mismo número de conexiones activas, se aplica el algoritmo round-robin.| -|Source|Este algoritmo realiza una función de *hash* en la dirección IP de origen y divide el resultado entre el número de servidores activos en ese momento. Cada dirección IP de origen siempre será dirigida al mismo servidor, mientras este permanezca activo.| -|URI|Este algoritmo realiza una función de *hash* en una parte de la URI (o en la URI entera) y divide el resultado entre el número de servidores activos en ese momento. Cada URI siempre será dirigida al mismo servidor, mientras este permanezca activo.| - -### Cambiar el modo de balanceo de la carga de una granja desde el área de cliente - -Una vez en la sección Cloud del área de cliente, haga clic en `Load Balancer`{.action} en la columna izquierda y seleccione el Load Balancer. - -Abra la pestaña `Granjas de servidores`{.action}. Se mostrarán las granjas de servidores existentes en ese momento. Para editar una, haga clic en los tres puntos situados a la derecha de la línea correspondiente y seleccione `Editar`{.action}. - -![Editar una granja](images/server_cluster_change.png){.thumbnail} - -En **Parámetros avanzados** podrá cambiar el modo de balanceo. - -![Editar una granja](images/distrib_mode_edit.png){.thumbnail} - -Una vez seleccionado el modo de balanceo, haga clic en `Actualizar`{.action} y, en la banda amarilla que aparecerá en la parte superior, haga clic en `Aplicar la configuración`{.action}. - -![Aplicar la configuración](images/apply_config.png){.thumbnail} - -### Cambiar el modo de balanceo de la carga de una granja a través de la API - -Para cambiar el modo de balanceo, es necesario editar los parámetros de la granja de servidores. - -#### Ver el detalle de una granja - -Esta llamada a la API permite consultar el detalle de una granja a partir de su identificador. En este ejemplo utilizamos una granja HTTP. - -> [!api] -> -> @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/http/farm/{farmId} -> - -|Parámetro|Significado| -|---|---| -|ServiceName*|Identificador del servicio Load Balancer| -|farmId*|Identificador numérico de la granja| - -|Respuesta (BackendHttp)|Significado| -|---|---| -|zone|Nombre de la zona en la que está configurada la granja| -|port|Puerto utilizado para conectar con los servidores configurados en la granja| -|farmId|Identificador numérico de la granja| -|balance|Tipo de balanceo actualmente configurado en la granja| -|probe|Tipo de sonda actualmente configurada en la granja| -|stickiness|Modo de seguimiento de conexión actualmente configurado en la granja| -|displayName|Nombre asignado a la granja| - -#### Cambiar el modo de balanceo de una granja - -Esta llamada a la API permite modificar la configuración de una granja a partir de su identificador. En este ejemplo utilizamos una granja HTTP. Para cambiar el modo de balanceo, es necesario actualizar el campo **BackendHttp.balance** con un modo de balanceo disponible. - -> [!api] -> -> @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/http/farm/{farmId} -> - -|Parámetro|Significado| -|---|---| -|serviceName*|Identificador del servicio Load Balancer| -|farmId*|Identificador numérico de la granja| -|BackendHttp.balance|Tipo de balanceo deseado para la granja| - -#### Aplicar los cambios - -> [!api] -> -> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh -> - -|Parámetro|Significado| -|---|---| -|serviceName*|Identificador del servicio Load Balancer| -|zone|Nombre de la zona en la que desea desplegar la configuración| - -## Más información - -Interactúe con nuestra comunidad de usuarios en . \ No newline at end of file diff --git a/pages/network/load_balancer/create_balancing/guide.es-us.md b/pages/network/load_balancer/create_balancing/guide.es-us.md deleted file mode 100644 index a8e597376be..00000000000 --- a/pages/network/load_balancer/create_balancing/guide.es-us.md +++ /dev/null @@ -1,107 +0,0 @@ ---- -title: 'Modos de balanceo' -excerpt: 'Modos de balanceo de la carga del Load Balancer de OVH' -updated: 2018-01-17 ---- - -## Objetivo - -El nuevo Load Balancer de OVH ofrece distintos tipos de balanceo de la carga de los servicios, que determinan la forma en la que las peticiones recibidas se distribuyen entre los servidores. - -**Esta guía explica los distintos tipos de balanceo de carga y cómo cambiar entre ellos.** - -## Requisitos - -- Estar conectado al [área de cliente de OVH](/links/manager). -- Haber creado una granja de servidores. - -## Procedimiento - -### Tipos de balanceo de la carga - -En las granjas de servidores, el balanceo de carga determina la forma en la que las peticiones se distribuirán entre los distintos servidores de la granja. - -Para conocer las principales características del Load Balancer de OVH, consulte la [guía de presentación del servicio](/pages/network/load_balancer/use_presentation). - -|Algoritmo|Funcionalidades| -|---|---| -|Round-robin|Elige un servidor tras otro en cada conexión. Es el algoritmo utilizado por defecto.| -|First|El primer servidor disponible recibe la conexión. El orden de los servidores se elige en función de su ID, de menor a mayor.| -|Least|Elige el servidor con menos conexiones activas. Se recomienda elegir este algoritmo para sesiones prolongadas con poco tráfico. En los grupos de servidores que tienen el mismo número de conexiones activas, se aplica el algoritmo round-robin.| -|Source|Este algoritmo realiza una función de *hash* en la dirección IP de origen y divide el resultado entre el número de servidores activos en ese momento. Cada dirección IP de origen siempre será dirigida al mismo servidor, mientras este permanezca activo.| -|URI|Este algoritmo realiza una función de *hash* en una parte de la URI (o en la URI entera) y divide el resultado entre el número de servidores activos en ese momento. Cada URI siempre será dirigida al mismo servidor, mientras este permanezca activo.| - -### Cambiar el modo de balanceo de la carga de una granja desde el área de cliente - -Una vez en la sección Cloud del área de cliente, haga clic en `Load Balancer`{.action} en la columna izquierda y seleccione el Load Balancer. - -Abra la pestaña `Granjas de servidores`{.action}. Se mostrarán las granjas de servidores existentes en ese momento. Para editar una, haga clic en los tres puntos situados a la derecha de la línea correspondiente y seleccione `Editar`{.action}. - -![Editar una granja](images/server_cluster_change.png){.thumbnail} - -En **Parámetros avanzados** podrá cambiar el modo de balanceo. - -![Editar una granja](images/distrib_mode_edit.png){.thumbnail} - -Una vez seleccionado el modo de balanceo, haga clic en `Actualizar`{.action} y, en la banda amarilla que aparecerá en la parte superior, haga clic en `Aplicar la configuración`{.action}. - -![Aplicar la configuración](images/apply_config.png){.thumbnail} - -### Cambiar el modo de balanceo de la carga de una granja a través de la API - -Para cambiar el modo de balanceo, es necesario editar los parámetros de la granja de servidores. - -#### Ver el detalle de una granja - -Esta llamada a la API permite consultar el detalle de una granja a partir de su identificador. En este ejemplo utilizamos una granja HTTP. - -> [!api] -> -> @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/http/farm/{farmId} -> - -|Parámetro|Significado| -|---|---| -|ServiceName*|Identificador del servicio Load Balancer| -|farmId*|Identificador numérico de la granja| - -|Respuesta (BackendHttp)|Significado| -|---|---| -|zone|Nombre de la zona en la que está configurada la granja| -|port|Puerto utilizado para conectar con los servidores configurados en la granja| -|farmId|Identificador numérico de la granja| -|balance|Tipo de balanceo actualmente configurado en la granja| -|probe|Tipo de sonda actualmente configurada en la granja| -|stickiness|Modo de seguimiento de conexión actualmente configurado en la granja| -|displayName|Nombre asignado a la granja| - -#### Cambiar el modo de balanceo de una granja - -Esta llamada a la API permite modificar la configuración de una granja a partir de su identificador. En este ejemplo utilizamos una granja HTTP. Para cambiar el modo de balanceo, es necesario actualizar el campo **BackendHttp.balance** con un modo de balanceo disponible. - -> [!api] -> -> @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/http/farm/{farmId} -> - -|Parámetro|Significado| -|---|---| -|serviceName*|Identificador del servicio Load Balancer| -|farmId*|Identificador numérico de la granja| -|BackendHttp.balance|Tipo de balanceo deseado para la granja| - -#### Aplicar los cambios - -> [!api] -> -> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh -> - -|Parámetro|Significado| -|---|---| -|serviceName*|Identificador del servicio Load Balancer| -|zone|Nombre de la zona en la que desea desplegar la configuración| - -## Más información - -Interactúe con nuestra comunidad de usuarios en . \ No newline at end of file diff --git a/pages/network/load_balancer/create_balancing/guide.fr-ca.md b/pages/network/load_balancer/create_balancing/guide.fr-ca.md index f88fe19a84e..642b33791f2 100644 --- a/pages/network/load_balancer/create_balancing/guide.fr-ca.md +++ b/pages/network/load_balancer/create_balancing/guide.fr-ca.md @@ -1,7 +1,7 @@ --- title: Modes de répartition excerpt: Découvrez les différents modes de répartition de charge du Load Balancer OVHcloud -updated: 2025-10-23 +updated: 2025-10-24 --- ## Objectif diff --git a/pages/network/load_balancer/create_balancing/guide.fr-fr.md b/pages/network/load_balancer/create_balancing/guide.fr-fr.md index f88fe19a84e..642b33791f2 100644 --- a/pages/network/load_balancer/create_balancing/guide.fr-fr.md +++ b/pages/network/load_balancer/create_balancing/guide.fr-fr.md @@ -1,7 +1,7 @@ --- title: Modes de répartition excerpt: Découvrez les différents modes de répartition de charge du Load Balancer OVHcloud -updated: 2025-10-23 +updated: 2025-10-24 --- ## Objectif diff --git a/pages/network/load_balancer/create_balancing/guide.it-it.md b/pages/network/load_balancer/create_balancing/guide.it-it.md deleted file mode 100644 index 9d94c5e9bf3..00000000000 --- a/pages/network/load_balancer/create_balancing/guide.it-it.md +++ /dev/null @@ -1,105 +0,0 @@ ---- -title: 'Modalità di ripartizione' -excerpt: 'Scopri le diverse modalità di ripartizione del carico dell’OVH Load Balancer' -updated: 2018-01-17 ---- - -## Obiettivo - -La nuova soluzione OVH Load Balancer offre diverse tipologie di ripartizione del carico per i tuoi servizi. Questo processo determina il modo in cui l’OVH Load Balancer ripartisce le richieste ricevute verso i tuoi server. - -**Questa guida ti mostra i diversi tipi di ripartizione del carico e ti spiega come modificarli.** - -## Prerequisiti - -- Avere accesso allo [Spazio Cliente OVH](/links/manager) -- Disporre di una server farm - -## Procedura - -### Le diverse tipologie di ripartizione del carico - -La ripartizione del carico si utilizza nelle server farm. Attraverso questo parametro si definisce il modo in cui le richieste vengono suddivise tra i server della farm. - -Per saperne di più sul servizio OVH Load Balancer, consulta la seguente guida: [Presentazione Load Balancer](/pages/network/load_balancer/use_presentation). - -|Algoritmo|Caratteristiche| -|---|---| -|First|Il primo server disponibile riceve la connessione. La scelta del server avviene in base all’ID, dal più piccolo al più grande.| -|LeastConn|Seleziona il server con il numero minore di connessioni attive: è l’opzione suggerita per lunghe sessioni con poco traffico. L'algoritmo *RoundRobin* si applica sui gruppi di server con lo stesso numero di connessioni attive.| -|RoundRobin|Seleziona i server uno dopo l’altro per ciascuna connessione, **è l’algoritmo di default.**| -|Source|Questo algoritmo ha una funzione di *hash* sull’indirizzo IP di origine e divide il risultato per il numero di server attivi in quel preciso momento. Lo stesso indirizzo IP di origine verrà quindi sempre reindirizzato verso lo stesso server, fino a quando questo resterà attivo.| -|URI|Questo algoritmo ha una funzione di *hash* su una parte dell’URI (o sull’URI per intero) e divide il risultato per il numero dei server attivi in quel preciso momento. Lo stesso URI verrà quindi sempre reindirizzato verso lo stesso server fino a quando questo resterà attivo.| - -### Modifica la modalità di ripartizione del carico di una server farm attraverso lo Spazio Cliente - -- Nella sezione `Server farm`{.action} (1) puoi visualizzare le farm precedentemente create. è sufficiente modificarne una cliccando sui tre puntini a destra (2) poi su `Modifica`{.action} (3): - -![Modification d'une ferme](images/server_cluster_change.png){.thumbnail} - -Nella sezione `Opzioni avanzate`{.action} puoi modificare la `Modalità di ripartizione`{.action}: - -![Modification d'une ferme](images/distrib_mode_edit.png){.thumbnail} - -Una volta modificata la modalità di ripartizione, clicca su `Aggiorna`{.action}, e poi su `Applica la configurazione`{.action} nella barra gialla che apparirà in alto: - -![Attivazione della configurazione](images/apply_config.png){.thumbnail} - -### Modifica la modalità di ripartizione del carico di una server farm via API - -Per cambiare i parametri della modalità di ripartizione attraverso le API è necessario modificare la configurazione della server farm. - -- Una server farm nel dettaglio - -Questa chiamata API consente di consultare il dettaglio di una farm a partire dal relativo identificativo. In questo esempio utilizziamo una farm HTTP: - -> [!api] -> -> @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/http/farm/{farmId} -> - -|Parametro|Significato| -|---|---| -|ServiceName*|Identificativo del tuo servizio Load Balancer| -|farmId*|Identificativo numerico della farm| - -|Risposta (BackendHttp)|Significato| -|---|---| -|farmId|Identificativo numerico della farm| -|balance|Tipo di ripartizione attualmente configurato sulla farm| -|zone|Nome della zona in cui è stata configurata la farm| -|port|Porta utilizzata per contattare i server configurati sulla farm| -|probe|Tipo di sonda attualmente configurata sulla farm| -|displayName|Nome assegnato a questa farm| -|stikiness|Modalità di monitoraggio della connessione attualmente configurato sulla farm| - -- Modifica la modalità di ripartizione di una server farm - -Questa chiamata API consente di consultare il dettaglio di una farm a partire dal relativo identificativo. In questo esempio utilizziamo una farm HTTP: Per modificare la modalità di ripartizione, è necessario aggiornare il campo `BackendHttp.balance` con una modalità di ripartizione disponibile: - -> [!api] -> -> @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/http/farm/{id} -> - -|Parametro|Significato| -|---|---| -|ServiceName*|Identificativo del tuo servizio Load Balancer| -|farmId*|Identificativo numerico della farm| -|BackendHttp.balance|Tipo di ripartizione preferita per questa farm| - -- Applica le modifiche - -> [!api] -> -> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh -> - -|Parametro|Significato| -|---|---| -|ServiceName*|Identificativo del tuo servizio Load Balancer| -|zone*|Nome della zona in cui distribuire la configurazione| - -## Per saperne di più - -Contatta la nostra Community di utenti all’indirizzo . diff --git a/pages/network/load_balancer/create_balancing/guide.pl-pl.md b/pages/network/load_balancer/create_balancing/guide.pl-pl.md deleted file mode 100644 index cc922e077b2..00000000000 --- a/pages/network/load_balancer/create_balancing/guide.pl-pl.md +++ /dev/null @@ -1,106 +0,0 @@ ---- -title: Sposoby równoważenia obciążenia -excerpt: Poznaj różne sposoby równoważenia obciążenia dostępne w usłudze Load Balancer -updated: 2018-01-17 ---- - -## Wprowadzenie - -Nowa usługa Load Balancer oferuje różne typy równoważenia obciążenia (load balancingu) dla Twoich usług. Opisany proces określa sposób, w jaki Load Balancer będzie rozdzielał zapytania kierowane do Twoich serwerów. - -**Niniejszy przewodnik przedstawia różne typy równoważenia obciążenia i wyjaśnia, jak je modyfikować.** - -## Wymagania początkowe - -- Dostęp do [Panelu klienta OVH](/links/manager) -- Aktywna usługa Load Balancer -- Utworzona farma serwerów - -## W praktyce - -### Różne typy równoważenia obciążenia - -Równoważenie obciążenia realizowane jest w farmach serwerów. Poniżej podane są parametry, które określają sposób, w jaki zapytania są rozdzielane między serwery danej farmy. - -Poznaj podstawowe części składowe usługi w [przewodniku prezentującym Load Balancer](/pages/network/load_balancer/use_presentation). - -|Algorytm|Funkcje| -|---|---| -|First|Pierwszy dostępny serwer otrzymuje połączenie. Serwer jest wybierany według jego ID, od najniższego numeru do najwyższego. | -|LeastConn|Wybierz serwer, który ma najmniej aktywnych połączeń. Jest to parametr zalecany w przypadku długich sesji i niewielkiego ruchu. Algorytm*RoundRobin* stosowany jest w grupach serwerów mających tę samą liczbę aktywnych połączeń.| -|RoundRobin|Połączenia są przekazywane, kolejno do każdego serwera, **to algorytm domyślny.**| -|Source|Algorytm wykonuje funkcję *hash* na źródłowym adresie IP, następnie dzieli wynik przez liczbę serwerów aktywnych w danym momencie. Ten sam źródłowy adres IP będzie zawsze przekierowywany do tego samego serwera, dopóki pozostaje on aktywny.| -|URI|Algorytm wykonuję funkcję *hash* na części lub całości URI, następnie dzieli wynik przez liczbę serwerów aktywnych w danym momencie. Ten sam URI będzie zawsze przekierowywany do tego samego serwera, dopóki pozostaje on aktywny.| - -### Modyfikacja sposobu równoważenia obciążenia farmy w Panelu klienta - -- Sprawdź utworzone farmy w sekcji `Farmy serwerów`{.action} (1). Edytuj wybraną farmę, klikając trzy kropki, oznaczające rozwijane menu, po prawej stronie (2), a następnie kliknij `Modyfikuj`{.action} : - -![Modyfikacja farmy](images/server_cluster_change.png){.thumbnail} - - `Sposób równoważenia obciążenia`{.action} możesz zmienić w `Ustawieniach zaawansowanych`{.action}: - -![Modyfikacja farmy](images/distrib_mode_edit.png){.thumbnail} - -Po wybraniu sposobu równoważenia obciążenia kliknij `Aktualizacja`{.action}, a następnie `Zastosuj konfigurację`{.action} na żółtym pasku, który się pojawi: - -![Zastosuj konfigurację](images/apply_config.png){.thumbnail} - -### Modyfikacja sposobu równoważenia obciążenia farmy przez API - -Modyfikacja ustawień sposobu równoważenia obciążenia następuje po zmianie ustawień farmy serwerów. - -- Zobacz szczegóły dotyczące farmy. - -Komenda ta pozwala wyświetlić szczegóły dotyczące farmy serwerów po wpisaniu jej identyfikatora. Operacja została przedstawiona poniżej na przykładzie farmy HTTP. - -> [!api] -> -> @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/http/farm/{farmId} -> - -|Parametr|Opis| -|---|---| -|ServiceName*|Identyfikator Twojej usługi Load Balancer| -|farmId*|Identyfikator numeryczny farmy| - -|Odpowiedź (BackendHttp)|Opis| -|---|---| -|farmId|Identyfikator numeryczny farmy| -|balance|Typ równoważenia obciążenia obecnie skonfigurowany dla farmy| -|zone|Nazwa strefy, w której skonfigurowana jest farma| -|port|port używany do łączenia się z serwerami skonfigurowanymi w farmie| -|probe|Typ sondy skonfigurowanej w farmie| -|displayName|Nazwa nadana tej farmie| -|stickiness|Sposób połączenia skonfigurowany w farmie| - -- Zmodyfikuj sposób równoważenia obciążenia farmy. - -Komenda ta pozwala zmodyfikować konfigurację farmy po wpisaniu jej identyfikatora. Operacja została przedstawiona poniżej na przykładzie farmy HTTP: Aby zmodyfikować sposób równoważenia obciążenia, zaktualizuj pole `BackendHttp.balance`, wpisując dostępny sposób równoważenia: - -> [!api] -> -> @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/http/farm/{id} -> - -|Parametr|Opis| -|---|---| -|ServiceName*|Identyfikator Twojej usługi Load Balancer| -|farmId*|Identyfikator numeryczny farmy| -|BackendHttp.balance|Typ równoważenia wybrany dla tej farmy| - -- Zastosuj modyfikacje. - -> [!api] -> -> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh -> - -|Parametr|Opis| -|---|---| -|ServiceName*|Identyfikator Twojej usługi Load Balancer| -|zone*|Nazwa strefy do konfiguracji| - -## Sprawdź również - -Przyłącz się do społeczności naszych użytkowników na stronie . diff --git a/pages/network/load_balancer/create_balancing/guide.pt-pt.md b/pages/network/load_balancer/create_balancing/guide.pt-pt.md deleted file mode 100644 index d5af737a31b..00000000000 --- a/pages/network/load_balancer/create_balancing/guide.pt-pt.md +++ /dev/null @@ -1,105 +0,0 @@ ---- -title: 'Método de repartição' -excerpt: 'Conheça os diferentes métodos de repartição de carga do Load Balancer OVH' -updated: 2018-01-17 ---- - -## Sumário - -O novo Load Balancer OVH oferece diferentes tipos de repartição de carga para os seus serviços. Este processo determina a forma como o Load Balancer OVH distribui os pedidos recebidos pelos seus servidores. - -**Este guia apresenta os diferentes tipos de repartição de carga e explica como modificá-los.** - -## Requisitos - -- Ter acesso à [Área de Cliente OVH](/links/manager). -- Ter uma Farm de servidores criada. - -## Instruções - -### Os diferentes tipos de repartição de carga - -A repartição de carga é utilizada nas Farms de servidores. É este parâmetro que define a forma como os pedidos são distribuídos entre os servidores da Farm. - -Para conhecer os principais elementos do Load Balancer OVH, consulte [Apresentação do Load Balancer](/pages/network/load_balancer/use_presentation). - -|Algoritmo|Funcionalidades| -|---|---| -|First|O primeiro servidor disponível recebe a conexão. O servidor é escolhido em função do seu ID, do menor ao maior.| -LeastConn|Seleciona o servidor que tem menos conexões ativas. Este parâmetro é recomendado para sessões longas com pouco tráfego. O algortimo *RoundRobin* é aplicado aos grupos de servidores que têm o mesmo número de conexões ativas.| -|RoundRobin|Seleciona os servidores um após o outro para cada conexão. **Este é o algoritmo usado por defeito.**| -|Source|Este algoritmo efetua uma função de *hash* no endereço IP de origem e a seguir divide o resultado pelo número de servidores atualmente ativos. Cada endereço IP de origem será então redirigido para o mesmo servidor, enquanto este continuar ativo.| -|URI|Este algoritmo efetua uma função de *hash* numa parte da URI, ou na URI inteira, e a seguir divide o resultado pelo número de servidores atualmente ativos. Cada URI será então redirigida para o mesmo servidor, enquanto este continuar ativo.| - -### Modificar o método de repartição de carga de uma Farm através da Área de Cliente - -- Na secção `Server farms`{.action} (1), verá as Farms já criadas. Basta editar uma delas clicando nos três pontos à direita (2) e depois em `Change`{.action}: - -![Modificação de uma Farm](images/server_cluster_change.png){.thumbnail} - -Em `Advanced settings`{.action}, poderá modificar o `Load balancing method`{.action}: - -![Modificação de uma Farm](images/distrib_mode_edit.png){.thumbnail} - -Quando tiver selecionado o método de repartição desejado, clique em `Update`{.action} e depois em `Apply configuration`{.action} na barra amarela que surgir: - -![Aplicar a configuração ](images/apply_config.png){.thumbnail} - -### Modificar o método de repartição de carga de uma Farm através da API - -Para modificar os parâmetros do método de repartição, edite os parâmetros da Farm de servidores. - -- Ver detalhes de uma Farm - -Esta instrução permite consultar detalhes de uma Farm se conhecer o seu ID. Neste exemplo, vamos trabalhar sobre uma Farm HTTP: - -> [!api] -> -> @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/http/farm/{farmId} -> - -|Parâmetro|Significado| -|---|---| -|ServiceName*|ID do serviço Load Balancer| -|farmId*|ID da Farm| - -|Resposta (BackendHttp)|Significado| -|---|---| -|farmId|ID da Farm| -|balance|Tipo de repartição atualmente configurado para a Farm| -|zone|Nome da zona em que está configurada a Farm| -|port|Porta usada para ligar aos servidores configurados na Farm| -|probe|Tipo de probe atualmente configurado para a Farm| -|displayName|Nome dado a esta Farm| -|stikiness|Modo de monitoramento de conexão atualmente configurado para a Farm| - -- Modificar o método de repartição de uma Farm - -Esta instrução permite modificar a configuração de uma Farm se conhecer o seu ID. Neste exemplo, vamos trabalhar sobre uma Farm HTTP. Para modificar o método de repartição, o campo `BackendHttp.balance` deve ser atualizado com um método de repartição disponível: - -> [!api] -> -> @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/http/farm/{id} -> - -|Parâmetro|Significado| -|---|---| -|ServiceName*|ID do serviço Load Balancer| -|farmId*|ID da Farm| -|BackendHttp.balance|Tipo de repartição desejado para esta Farm| - -- Aplicar as modificações - -> [!api] -> -> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh -> - -|Parâmetro|Significado| -|---|---| -|ServiceName*|ID do Load Balancer| -|zone*|Nome da zona na qual deseja aplicar a configuração| - -## Quer saber mais? - -Fale com a nossa comunidade de utilizadores: . diff --git a/pages/network/load_balancer/order_freecertificate/guide.en-asia.md b/pages/network/load_balancer/order_freecertificate/guide.en-asia.md index 0dc26599f11..e3bfced3f83 100644 --- a/pages/network/load_balancer/order_freecertificate/guide.en-asia.md +++ b/pages/network/load_balancer/order_freecertificate/guide.en-asia.md @@ -1,7 +1,7 @@ --- title: Order a free SSL certificate excerpt: Order a free SSL certificate for your web services behind a Load Balancer -updated: 2025-10-23 +updated: 2025-10-24 --- ## Objective diff --git a/pages/network/load_balancer/order_freecertificate/guide.en-au.md b/pages/network/load_balancer/order_freecertificate/guide.en-au.md index 0dc26599f11..e3bfced3f83 100644 --- a/pages/network/load_balancer/order_freecertificate/guide.en-au.md +++ b/pages/network/load_balancer/order_freecertificate/guide.en-au.md @@ -1,7 +1,7 @@ --- title: Order a free SSL certificate excerpt: Order a free SSL certificate for your web services behind a Load Balancer -updated: 2025-10-23 +updated: 2025-10-24 --- ## Objective diff --git a/pages/network/load_balancer/order_freecertificate/guide.en-ca.md b/pages/network/load_balancer/order_freecertificate/guide.en-ca.md index 0dc26599f11..e3bfced3f83 100644 --- a/pages/network/load_balancer/order_freecertificate/guide.en-ca.md +++ b/pages/network/load_balancer/order_freecertificate/guide.en-ca.md @@ -1,7 +1,7 @@ --- title: Order a free SSL certificate excerpt: Order a free SSL certificate for your web services behind a Load Balancer -updated: 2025-10-23 +updated: 2025-10-24 --- ## Objective diff --git a/pages/network/load_balancer/order_freecertificate/guide.en-gb.md b/pages/network/load_balancer/order_freecertificate/guide.en-gb.md index 0dc26599f11..e3bfced3f83 100644 --- a/pages/network/load_balancer/order_freecertificate/guide.en-gb.md +++ b/pages/network/load_balancer/order_freecertificate/guide.en-gb.md @@ -1,7 +1,7 @@ --- title: Order a free SSL certificate excerpt: Order a free SSL certificate for your web services behind a Load Balancer -updated: 2025-10-23 +updated: 2025-10-24 --- ## Objective diff --git a/pages/network/load_balancer/order_freecertificate/guide.en-sg.md b/pages/network/load_balancer/order_freecertificate/guide.en-sg.md index 0dc26599f11..e3bfced3f83 100644 --- a/pages/network/load_balancer/order_freecertificate/guide.en-sg.md +++ b/pages/network/load_balancer/order_freecertificate/guide.en-sg.md @@ -1,7 +1,7 @@ --- title: Order a free SSL certificate excerpt: Order a free SSL certificate for your web services behind a Load Balancer -updated: 2025-10-23 +updated: 2025-10-24 --- ## Objective diff --git a/pages/network/load_balancer/order_freecertificate/guide.en-us.md b/pages/network/load_balancer/order_freecertificate/guide.en-us.md index 0dc26599f11..e3bfced3f83 100644 --- a/pages/network/load_balancer/order_freecertificate/guide.en-us.md +++ b/pages/network/load_balancer/order_freecertificate/guide.en-us.md @@ -1,7 +1,7 @@ --- title: Order a free SSL certificate excerpt: Order a free SSL certificate for your web services behind a Load Balancer -updated: 2025-10-23 +updated: 2025-10-24 --- ## Objective diff --git a/pages/network/load_balancer/order_freecertificate/guide.fr-ca.md b/pages/network/load_balancer/order_freecertificate/guide.fr-ca.md index 9f4c85e5c03..b6342afa209 100644 --- a/pages/network/load_balancer/order_freecertificate/guide.fr-ca.md +++ b/pages/network/load_balancer/order_freecertificate/guide.fr-ca.md @@ -1,7 +1,7 @@ --- title: "Commande d'un certificat SSL gratuit" excerpt: Commander un certificat SSL gratuit pour vos services web derrière un Load Balancer -updated: 2025-10-23 +updated: 2025-10-24 --- ## Objectif diff --git a/pages/network/load_balancer/order_freecertificate/guide.fr-fr.md b/pages/network/load_balancer/order_freecertificate/guide.fr-fr.md index 9f4c85e5c03..b6342afa209 100644 --- a/pages/network/load_balancer/order_freecertificate/guide.fr-fr.md +++ b/pages/network/load_balancer/order_freecertificate/guide.fr-fr.md @@ -1,7 +1,7 @@ --- title: "Commande d'un certificat SSL gratuit" excerpt: Commander un certificat SSL gratuit pour vos services web derrière un Load Balancer -updated: 2025-10-23 +updated: 2025-10-24 --- ## Objectif From 8e7237cbe2152f0aebfce5e171c2abfd3016e7df Mon Sep 17 00:00:00 2001 From: Yoann Cosse Date: Fri, 24 Oct 2025 17:37:55 +0200 Subject: [PATCH 22/23] Deleting LLM --- llm-config/config.json | 34 --- llm-config/system-prompts/generation.md | 70 ------ llm-config/system-prompts/guide-refinement.md | 30 --- llm-config/system-prompts/guide-to-prompt.md | 109 --------- llm-config/system-prompts/translation.md | 63 ----- llm-config/terminology/translations.csv | 215 ------------------ 6 files changed, 521 deletions(-) delete mode 100644 llm-config/config.json delete mode 100644 llm-config/system-prompts/generation.md delete mode 100644 llm-config/system-prompts/guide-refinement.md delete mode 100644 llm-config/system-prompts/guide-to-prompt.md delete mode 100644 llm-config/system-prompts/translation.md delete mode 100644 llm-config/terminology/translations.csv diff --git a/llm-config/config.json b/llm-config/config.json deleted file mode 100644 index 85442280015..00000000000 --- a/llm-config/config.json +++ /dev/null @@ -1,34 +0,0 @@ -{ - "runMidscene": { - "model": "Qwen2.5-VL-72B-Instruct", - "configuration": { - "baseURL": "https://oai.endpoints.preprod.ai.cloud.ovh.net/v1", - "cache": "1" - } - }, - "translateGuide": { - "model": "Qwen3-32B", - "configuration": { - "baseURL": "https://oai.endpoints.preprod.ai.cloud.ovh.net/v1" - }, - "maxTokens": 4000, - "temperature": 0.2 - }, - "generateGuide": { - "model": "Meta-Llama-3_3-70B-Instruct", - "configuration": { - "baseURL": "https://oai.endpoints.preprod.ai.cloud.ovh.net/v1" - }, - "maxTokens": 5000, - "temperature": 0.2, - "topP": 1 - }, - "guideToPrompt": { - "model": "Meta-Llama-3_3-70B-Instruct", - "configuration": { - "baseURL": "https://oai.endpoints.preprod.ai.cloud.ovh.net/v1" - }, - "maxTokens": 5000, - "temperature": 0.2 - } -} diff --git a/llm-config/system-prompts/generation.md b/llm-config/system-prompts/generation.md deleted file mode 100644 index a6a502ad84d..00000000000 --- a/llm-config/system-prompts/generation.md +++ /dev/null @@ -1,70 +0,0 @@ -**Technical Writing Task** - -Act as a technical writer to create a comprehensive guide based on the provided steps. Ensure that the text is logical, clear, and concise, making it easily understandable for both technical and non-technical readers. - -**Guide Requirements** - -- Write the guide in the specified language: {{locale}} -- Improve the text in terms of clarity, quality, and readability -- Use footnotes to explain technical terms related to the computer domain -- Adhere to industry standards for technical documentation -- Ensure the guide is concise and easy to follow - -**Guide Details** - -- Guide name: {{scenario}} -- Base URL: {{base_url}} (to be mentioned in the first step) -- add balise before first step - -**Steps** - -Here is the list of steps the playwright AI agent follows -in order to perform the actions explained in the guide: - -```yaml -{{steps}} -``` - -Note that each step provided should not necessarily be -a step of the guide. - -For `screenshot` steps, do not write any text, -instead generate a markdown image using path, filename -and, if provided, description, right after the last previous step. - -Example format: - -```markdown - -![Descriptive alt text inspired by description or filename](path/filename) - -``` - -**Additional Requirements** - -- No need to number steps, just give them a title -- Provide additional information and context in each step to enhance clarity -- Include a header and footer with relevant information -- Use Markdown format for the guide -- Do not add scrolling steps -- Skip a line between each steps - {{custom_instructions}} - -**Document Header** - -Each document should begin with the following header: - -```markdown ---- -title: "Add a meaningful title here (generated by AI)" -excerpt: "Add a meta description of the guide" -updated: {{date}} -flag: hidden ---- -``` - -**Output Format** - -The output must be in valid Markdown format, do not encapsulate the result in a fenced code block. - -Please create the guide based on the provided steps, following the requirements and guidelines above. diff --git a/llm-config/system-prompts/guide-refinement.md b/llm-config/system-prompts/guide-refinement.md deleted file mode 100644 index 86f22819088..00000000000 --- a/llm-config/system-prompts/guide-refinement.md +++ /dev/null @@ -1,30 +0,0 @@ -**Guide Refinement Task** - -Act as a technical editor to polish the provided guide. Make minimal but impactful improvements to enhance readability while preserving the original structure and content. - -**Input** - -```markdown -{{guide}} -``` - -**Your Task** - -Review the guide and make light edits to: - -- Remove any obviously redundant or unnecessary sentences -- Simplify overly complex phrasing while keeping technical accuracy -- Ensure the tone feels natural and professional (not robotic) -- Fix any grammatical or stylistic issues - -**Important Constraints** - -- Keep all steps and their titles intact unless truly redundant -- Preserve all technical details, footnotes, and formatting -- Maintain the document header and structure -- Do not reorganize or heavily rewrite content -- Make only essential improvements - -**Output Format** - -Provide the refined guide in valid Markdown format. Do not encapsulate the result in a fenced code block. diff --git a/llm-config/system-prompts/guide-to-prompt.md b/llm-config/system-prompts/guide-to-prompt.md deleted file mode 100644 index e13cffd43d7..00000000000 --- a/llm-config/system-prompts/guide-to-prompt.md +++ /dev/null @@ -1,109 +0,0 @@ -**Task: Convert User Guide into Bot Actions** - -Your goal is to break down a given user guide into a series of steps that a browser-manipulating bot can follow. Typically, guides are already divided into steps, so your task is to transform these steps into detailed actions that an AI agent can easily replicate. -Note that you will be already logged in when accessing OVHcloud manager, so you don't need to add steps concerning authentification. -Links described as "/link/manager" corresponds to "https://www.ovh.com/manager/#/" -Note that your name as a user will be "POC Guides". - -**Requirements:** - -1. Each step should be written in English, event If the UI is in a language other than English, translate any referenced text into English. -2. Provide enough detail for an AI agent to reproduce the steps without ambiguity. -3. When a value needs to be filled, it should be valid. -4. Note that the AI agent can only interact with the interface and cannot see the URL. - -**Input:** - -The user guide to be converted is provided below: - -```md -{{guide}} -``` - -**Output Format:** - -The output should be in the following format: - -```json -{ - "target": { - "url": "https://website.com/exact-path", - "viewportWidth": 1280, - "viewportHeight": 720 - }, - "tasks": [ - { - "name": "Task Name", - "flow": [ - { - "type": "aiWaitFor", - "action": "Perform action 1" - }, - { - "type": "ai", - "action": "Perform action 2" - } - ] - } - ] -} -``` - -**Example:** - -For reference, here is an example of what the output might look like: - -```json -{ - "target": { - "url": "https://url-of-the-starting-point", - "viewportWidth": 1280, - "viewportHeight": 720 - }, - "tasks": [ - { - "name": "How to change date of birth", - "flow": [ - { - "type": "aiWaitFor", - "action": "You are on the page 'My Account'" - }, - { - "type": "ai", - "action": "Click on 'My informations'" - }, - { - "type": "aiWaitFor", - "action": "Wait for the page to finish loading" - }, - { - "type": "ai", - "action": "Click on Edit" - }, - { - "type": "aiAssert", - "action": "The user information form should be visible" - }, - { - "type": "ai", - "action": "Click the 'Date of birth' or 'Birthday' field" - }, - { - "type": "ai", - "action": "Update the field with a random date" - }, - { - "type": "ai", - "action": "Click on confirm" - }, - { - "type": "aiWaitFor", - "action": "A confirmation text should appear" - } - ] - } - ] -} -``` - -Please convert the provided user guide into this format, following the requirements and guidelines above. diff --git a/llm-config/system-prompts/translation.md b/llm-config/system-prompts/translation.md deleted file mode 100644 index 0d5cd2d7ccf..00000000000 --- a/llm-config/system-prompts/translation.md +++ /dev/null @@ -1,63 +0,0 @@ -/set nothink - -You are a translation tool. Your purpose is to create an accurately translated output text from a guide markdown. - -Follow these steps: - -1. The source language is {{source_lang}}. -2. Proceed with the translation of the user input text into {{target_lang}}. Strictly follow the formatting instructions specified below. -3. Output ONLY the completed translated text without any additional commentary, explanations, or formatting markers. Just pure markdown and do not encapsulate response in code block. - -## Tone & Style - -The input text is of a technical nature, specifically: - -- How to use OVHcloud products (user instructions, FAQ, tutorial) - Do not alter the tone or style. Your goal is to provide an accurate translation of the input text. - -## Formatting instructions - -- The input text is formatted in Markdown. Leave all Markdown formatting intact. -- The input text might contain HTML tags. Leave all HTML tags exactly as they are. (example: ). -- The input text includes custom Markdown formats. Leave all Markdown formats and their markers intact. Here are examples: - - Page frontmatter - - Relative links to internal pages - - Relative links to images - - External links - - Triple forward slashes (usage example: /// details | ///) - - Custom Markdown formats identfied by: [!api], [!primary], [!warning], [!alert], [!success], [!tabs] - - Button labels, example: `Button label`{.action} - - Labels, example: `Label` -- The input text may contain french quotation marks: « ». Rewrite them into English quotation marks: "". - -## Translation exceptions - -- Preserve the content of code blocks (English). -- Do not translate HTML link fragments and anchors. -- The structure of the input text may often contain certain sections names which must have standardized translations. Refer to the "CSV-formatted list of sections" for the approved translations of these sections. Ensure that you use these exact translations consistently throughout the guide, without introducing any variations. -- Some terms are fixed for each target language. Use the "CSV-formatted listof fixed terminology" below as reference for the proper translated versions. Do not translate these terms differently. - -### CSV-formatted list of sections - -```csv -French;English;German;Spanish;Italian;Polish;Portuguese -Objectif;Objective;Ziel;Objetivo;Obiettivo;Wprowadzenie;Objetivo -Prérequis;Requirements;Voraussetzungen;Requisitos;Prerequisiti;Wymagania początkowe;Requisitos -En pratique;Instructions;In der praktischen Anwendung;Procedimiento;Procedura;W praktyce;Instruções -Aller plus loin;Go further;Weiterführende Informationen;Más información;Per saperne di più;Sprawdź również;Quer saber mais? -Échangez avec notre [communauté d'utilisateurs](/links/community).;Join our [community of users](/links/community).;Treten Sie unserer [User Community](/links/community) bei.;Interactúe con nuestra [comunidad de usuarios](/links/community).;Contatta la nostra [Community di utenti](/links/community).;Dołącz do [grona naszych użytkowników](/links/community).;Fale com a nossa [comunidade de utilizadores](/links/community). -``` - -### CSV-formatted list of fixed terminology - -```csv -{{terminology_translations}} -``` - -## Text to translate - -**CRITICAL: Output the translated content directly as raw markdown. Do NOT wrap your response in code blocks (```), do NOT add explanatory text before or after, and do NOT include phrases like "Here is the translation" or similar commentary. Also, do not try to fix the markdown in any way** - -```markdown -{{guide}} -``` diff --git a/llm-config/terminology/translations.csv b/llm-config/terminology/translations.csv deleted file mode 100644 index b4516bbdfba..00000000000 --- a/llm-config/terminology/translations.csv +++ /dev/null @@ -1,215 +0,0 @@ -German;English;Spanish;French;Italian;Polish;Portuguese -OVHcloud Kundencenter;OVHcloud Control Panel;área de cliente de OVHcloud;espace client OVHcloud;Spazio Cliente OVHcloud;Panel klienta OVHcloud;área de cliente OVHcloud -Zerto;Zerto;Zerto;Zerto;Zerto;Zerto;Zerto -Nutanix on OVHcloud;Nutanix on OVHcloud;Nutanix on OVHcloud;Nutanix on OVHcloud;Nutanix on OVHcloud;Nutanix on OVHcloud;Nutanix on OVHcloud -Performance 4;Performance 4;Performance 4;Performance 4;Performance 4;Performance 4;Perf 4 -Analytics Manager;Analytics Manager;Analytics Manager;Analytics Manager;Analytics Manager;Analytics Manager;Analytics Manager -Quota- und Regionmanagement;Quota and Region Management;Quota and Region Management;Quota and region management;Quota and Region Management;Quota and Region Management;Quota and Region Management -Boost;Boost;Boost;Boost;Boost;Boost;Boost -CDN;CDN;CDN;CDN;CDN;CDN;CDN -;water cooling;;watercooling;;; -Private Exchange;Private Exchange;Private Exchange;Private Exchange;Private Exchange;Private Exchange;Private Exchange -;retrieval-augmented generation;;génération augmentée par récupération;;; -;Special Terms and Conditions;;Conditions Particulières;;; -Classic Block Storage;Classic Block Storage;Classic;Classic Block Storage;Classic;Classic Block Storage;Classic Block Storage -Kafka;Kafka;Kafka;Kafka;Kafka;Kafka;Kafka -SAP HANA on Private Cloud;SAP HANA on Private Cloud;SAP HANA on Private Cloud;SAP HANA on Private Cloud;SAP HANA on Private Cloud;SAP HANA on Private Cloud;SAP HANA on Private Cloud -GPU;GPU;GPU;GPU;GPU;GPU;GPU -Cloud Disk Array;Cloud Disk Array;Cloud Disk Array;Cloud Disk Array;Cloud Disk Array;Cloud Disk Array;Cloud Disk Array -Elite;Elite;Elite;Elite;Elite;Elite;Elite -;;;Availability Zone;;Availability Zone; -Environmental Impact Tracker;Environmental Impact Tracker;Environmental Impact Tracker;Environmental Impact Tracker;Environmental Impact Tracker;Environmental Impact Tracker;Environmental Impact Tracker -OVHcloud Partner Program;OVHcloud Partner Program;OVHcloud Partner Program;OVHcloud Partner program;OVHcloud Partner Program;OVHcloud Partner Program;OVHcloud Partner program -;;;Réseau et sécurité;;Sieć i bezpieczeństwo; -;Email solutions;Soluciones de correo;Solutions e-mail;Soluzioni email;Rozwiązania poczty elektronicznej;Soluções de e-mail -Standard Support;Standard Support;Soporte Standard;Support Standard;Supporto Standard;Standard;Suporte Standard -Veeam Managed Backup;Veeam Managed Backup;Veeam Managed Backup;Veeam Managed Backup;Veeam Managed Backup;Veeam Backup Managed;Veeam Managed Backup -MySQL;MySQL;MySQL;MySQL;MySQL;MySQL;MySQL -High Speed Block Storage;High Speed Block Storage;High Speed;High Speed Block Storage;High Speed;High Speed Block Storage;High Speed Block Storage -OVHcloud Load Balancer;OVHcloud Load Balancer;Load Balancer de OVHcloud;OVHcloud Load Balancer;Load Balancer OVHcloud;OVHcloud Load Balancer;Load Balancer da OVHcloud -;;;Environmental Impact Tracker;;Environmental Impact Tracker; -Trusted Exchange;Trusted Exchange;Trusted Exchange;Trusted Exchange;Trusted Exchange;Trusted Exchange;Trusted Exchange -;Collaborative solutions;Soluciones colaborativas;Solutions collaboratives;Soluzioni collaborative;Rozwiązania do pracy zespołowej;Soluções colaborativas -Data Processing Engine;Data Processing Engine;Data Processing Engine;Data Processing Engine;Data Processing Engine;Data Processing Engine;Data Processing Engine -Kafka Connect;Kafka Connect;Kafka Connect;Kafka Connect;Kafka Connect;Kafka Connect;Kafka Connect -On-Prem Cloud Platform;On-Prem Cloud Platform;On-Prem Cloud Platform;On-Prem Cloud Platform;On-Prem Cloud Platform;On-Prem Cloud Platform;On-Prem Cloud Platform -Advanced Collaborative Suite;Advanced collaborative suite;Suite colaborativa Advanced;Suite collaborative Advanced;Suite collaborativa Advance;Advanced collaborative suite;Suite colaborativa Advanced -Cloud Web 1;Cloud Web 1;Cloud Web 1;Cloud Web 1;Cloud Web 1;Cloud Web 1;Cloud Web 1 -Local Zones;Local Zones;Local Zones;Local Zones;Local Zones;Local Zones;Local Zones -Volume Snapshot;Volume Snapshot;Volume Snapshot;Volume Snapshot;Volume Snapshot;Volume Snapshot;Volume Snapshot -CDN Security;CDN Security;CDN Security;CDN Security;CDN Security;CDN Security;CDN Security -CDN Advanced;CDN Advanced;CDN Advanced;CDN Advanced;CDN Advanced;CDN Advanced;CDN Advanced -Bring your own IP (BYOIP);Bring Your Own IP (BYOIP);Bring Your Own IP (BYOIP);Bring Your Own IP (BYOIP);Bring Your Own IP (BYOIP);Bring your own IP (BYOIP);Bring your own IP (BYOIP) -;business-critical information;;informations stratégique;;; -Hosted Private Cloud powered by Anthos;Hosted Private Cloud powered by Anthos;Hosted Private Cloud powered by Anthos;Hosted Private Cloud powered by Anthos;Hosted Private Cloud powered by Anthos;Hosted Private Cloud powered by Anthos;Hosted Private Cloud powered by Anthos -Backup;Backup;Backup;Backup;Backup;Backup;Backup -E-Mail Pro;Email Pro;Email Pro;E-mail Pro;Email Pro;E-mail Pro;E-mail Pro -Managed Big Data Cluster;Managed Big Data Cluster;Managed Big Data Cluster;Managed Big Data Cluster;Managed Big Data Cluster;Managed Big Data Cluster;Managed Big Data Cluster -Managed Private Registry;Managed Private Registry;Managed Private Registry;Managed Private Registry;Managed Private Registry;Managed Private Registry;Managed Private Registry -;Web Hosting;Hosting;Hébergements web;Hosting Web;Hosting;Alojamentos web -Scale;Scale;Scale;Scale;Scale;Scale;Scale -CDN Basic;CDN Basic;CDN Basic;CDN Basic;CDN Basic;CDN Basic;CDN Basic -;Network Services;Servicios de red;Services réseau;Servizi di rete;Usługi sieciowe;Serviços de rede -;Levels of support;Niveles de soporte;Niveaux de support;Livelli di supporto;Poziomy wsparcia;Níveis de suporte -Cold Archive;Cold Archive;Cold Archive;Cold Archive;Cold Archive;Cold Archive;Cold Archive -Object Storage;Object Storage;Object Storage;Object storage;Object Storage;Object Storage;Object Storage -Starter;Starter;Starter;Starter;Starter;Starter;Starter -;;;Offre packagée;;Oferta pakietowa; -Das private Netzwerk vRack;vRack private network;Red privada vRack;Réseau privé vRack;Rete privata vRack;Prywatna sieć vRack;Rede privada vRack -;compute resources;;ressources de calcul;;; -Start 10M;Start 10M;Start 10M;Start 10M;Start 10M;Start 10M;Start 10M -Performance Hosting;Performance Hosting;Hosting Performance;Hébergement Performance;Hosting Performance;Hosting Performance;Alojamento Performance -Cloud Webhosting;Cloud Web Hosting;Hosting Cloud Web;Hébergement Cloud Web;Hosting Cloud Web;Hosting Cloud Web;Alojamento Cloud Web -Control Center;Control Center;Control Center;Control Center;Control Center;Control Center;Control Center -Hosted Exchange;Hosted Exchange;Hosted Exchange;Hosted Exchange;Hosted Exchange;Hosted Exchange;Hosted Exchange -High Grade;High Grade;High Grade;High Grade;High Grade;High Grade;High Grade -Data Catalog;Data Catalog;Data Catalog;Data Catalog;Data Catalog;Data Catalog;Data Catalog -;;;Bare Metal Cloud;;Bare Metal Cloud; -IOPS;IOPS;IOPS;IOPS;IOPS;IOPS;IOPS -VPS;VPS;VPS;VPS;VPS;VPS;VPS -Additional IP;Additional IP;Additional IP;Additional IP;Additional IP;Additional IP;Additional IP -;Domain Name Registrant;;Titulaire d’un Nom de Domaine;;; -HYCU for ovhcloud;HYCU for ovhcloud;HYCU for ovhcloud;HYCU for ovhcloud;HYCU for ovhcloud;;HYCU for ovhcloud -OpenSearch;OpenSearch;OpenSearch;OpenSearch;OpenSearch;OpenSearch;OpenSearch -Trusted Zone;Trusted Zone;Trusted Zone;Zone de confiance;Trusted Zone;Trusted Zone;Zonas de Confiança -Enterprise File Storage;Enterprise File Storage;Enterprise File Storage;Enterprise File Storage;Enterprise File Storage;Enterprise File Storage;Enterprise File Storage -Private Image Catalog;Private Image Catalog;Private Image Catalog;Private Image catalog;Private Image Catalog;Private Image Catalog;Private Image Catalog -Managed Kubernetes Service;Managed Kubernetes Service;Managed Kubernetes Service;Managed Kubernetes Service;Managed Kubernetes;Managed Kubernetes;Managed Kubernetes Service -;Domain names;Dominios;Noms de domaine;Domini;Domeny;Nomes de domínio -SSL-Zertifikat "Sectigo DV";Sectigo DV SSL certificate;Certificado SSL Sectigo DV;Certificat SSL Sectigo DV;Certificato SSL Sectigo DV;Certyfikat SSL Sectigo DV;Certificado SSL Sectigo DV -;Web security;Protección web;Sécurité web;Sicurezza Web;Bezpieczeństwo sieci;Segurança web -;Guaranteed resources;Guaranteed Resources;Guaranteed resources;Guaranteed Resources;Guaranteed Resources;Guaranteed Resources -;;;PERFORMANCE 4;;Performance 4; -Public VCF as-a-Service;Public VCF as-a-Service;Public VCF as-a-Service;Public VCF as-a-Service;Public VCF as-a-Service;Public VCF as-a-Service;Public VCF as-a-Service -Game;Game;Game;Game;Game;Game;Game -OVHcloud Link Aggregation (OLA);OVHcloud Link Aggregation (OLA);OVHcloud Link Aggregation (OLA);OVHcloud Link Aggregation (OLA);OVHcloud Link Aggregation (OLA);OVHcloud Link Aggregation (OLA);OVHcloud Link Aggregation (OLA) -SharePoint;SharePoint;SharePoint;SharePoint;SharePoint;SharePoint;SharePoint -Enterprise Support;Enterprise Support;Soporte Enterprise;Support Enterprise;Supporto Enterprise;Enterprise;Suporte Enterprise -Rise;Rise;Rise;Rise;Rise;Rise;Rise -CDN Security;CDN Security;CDN Security;CDN Security;CDN Security;CDN Security;CDN Security -Lakehouse Manager;Lakehouse Manager;Lakehouse Manager;Lakehouse Manager;Lakehouse Manager;Lakehouse Manager;Lakehouse Manager -;conformance program;;programme de conformité;;; -Business Support;Business Support;Soporte Business;Support Business;Supporto Business;Business;Suporte Business -;Options;Opciones;Options;Opzioni;Opcje;Opções -;;;Sécurité web;;Bezpieczeństwo sieci; -OVHcloud AI Training;OVHcloud AI Training;OVHcloud AI Training;OVHcloud AI Training;OVHcloud AI Training;OVHcloud AI Training;OVHcloud AI Training -;Affiliates;;Sociétés Apparentées;;; -File Storage;File Storage;File storage;File storage;File Storage;File storage;File storage -Local Zone;Local Zone;Local Zone;Local Zone;Local Zone;Local Zone;Local Zone -Managed Veeam for VCD;Managed Veeam for VCD;Managed Veeam for VCD;Managed Veeam for VCD;Managed Veeam for VCD;Managed Veeam for VCD;Managed Veeam for VCD -Enterprise Cloud Databases;Enterprise Cloud Databases;Enterprise Cloud Databases;Enterprise Cloud Databases;Enterprise Cloud Databases;Enterprise Cloud Databases;Enterprise Cloud Databases -Logs Data Platform;Logs Data Platform;Logs Data Platform;Logs Data Platform;Logs Data Platform;Logs Data Platform;Logs Data Platform -Performance 1;Performance 1;Performance 1;Performance 1;Performance 1;Performance 1;Perf 1 -DDoS-Schutz-Infrastruktur;Anti-DDoS infrastructure;Infraestructura anti-DDoS;Infrastructure Anti-DDoS;Infrastruttura anti-DDoS;Infrastruktura Anty-DDoS;Infraestrutura Anti-DDoS -MongoDB;MongoDB;MongoDB;MongoDB;MongoDB;MongoDB;MongoDB -NVIDIA NGC Platform;NVIDIA NGC Platform;NVIDIA NGC Platform;NVIDIA NGC Platform;NVIDIA NGC Platform;NVIDIA NGC Platform;NVIDIA NGC Platform -So you Start;So you Start;So you Start;So you Start;So you Start;So you Start;So you Start -Data Processing;Data Processing;Data Processing;Data Processing;Data Processing;Data Processing;Data Processing -Applications Services;Applications Services;Applications Services;Applications Services;Applications Services;Applications Services;Applications Services -;Dedicated Servers;Servidores dedicados;Serveurs dédiés;Server dedicati;Serwery dedykowane;Servidores dedicados -Cassandra;Cassandra;Cassandra;Cassandra;Cassandra;Cassandra;Cassandra -Basic Hosting;Personal Hosting;Hosting Personal;Hébergement Perso;Hosting Personale;Hosting Perso;Alojamento Perso -;;;Sécurité des hôtes et services;;Bezpieczeństwo hostów i usług; -Archive;Archive;Archive;Archive;Archive;Archive;Archive -;;;PERFORMANCE 3;;Performance 3; -M3DB;M3DB;M3DB;M3DB;M3DB;M3DB;M3DB -;Public bandwidth;Ancho de banda público;Bande passante publique;Banda passante pubblica;Przepustowość do sieci publicznej;Largura de banda pública -SSL;SSL;SSL;SSL;SSL;SSL;SSL -Redis;Redis;Redis;Redis;Redis;Redis;Redis -Grafana;Grafana;Grafana;Grafana;Grafana;Grafana;Grafana -Performance 3;Performance 3;Performance 3;Performance 3;Performance 3;Performance 3;Perf 3 -PostgreSQL;PostgreSQL;PostgreSQL;PostgreSQL;PostgreSQL;PostgreSQL;PostgreSQL -Comfort;Comfort;Comfort;Comfort;Comfort;Comfort;Comfort -;;;Hosted Private Cloud powered by VMware;;Hosted Private Cloud powered by VMware; -AI Notebooks;AI Notebooks;AI Notebooks;AI Notebooks;AI Notebooks;AI Notebooks;AI Notebooks -Value;Value;Value;Value;Value;Value;Value -Instance Backup;Instance Backup;Instance Backup;Instance Backup;Instance Backup;Instance Backup;Instance Backup -;Project Management;Project Management;Project management;Project Management;Project Management;Project Management -;white area;;Zone blanche;;; -Marketplace;Marketplace;Marketplace;Marketplace;Marketplace;Marketplace;Marketplace -;Infrastructure protection;Protección de infraestructura;Protection de l'infrastructure;Protezione dell'infrastruttura;Ochrona infrastruktury;Proteção da infraestrutura -Public Image Catalog;Public Image Catalog;Public Image Catalog;Public Image catalog;Public Image Catalog;Public Image Catalog;Public Image Catalog -;;;Pack Nutanix Advanced;;Pakiet Nutanix Advanced; -;SSL certificate as-a-Service;Certificado SSL as a Service;Certificat SSL as a Service;SSL Certificate as a Service;Certyfikat SSL as a Service;Certificado SSL as a Service -;;;PERFORMANCE 2;;Performance 2; -Standard Object Storage;Standard Object Storage;Standard Object Storage;Standard Object Storage;Standard Object Storage;Standard Object Storage;Standard Object Storage -;Web Hosting options;Opciones de alojamiento web;Options hébergement web;Opzioni hosting Web;Opcje hostingu;Opções de alojamento web -;AI & Machine Learning;AI & Machine Learning;AI & machine learning;AI & Machine Learning;AI & Machine Learning;AI & Machine Learning -Trusted Zone;Trusted Zone;Trusted Zone;Zone de confiance;Trusted Zone;Trusted Zone;Zonas de Confiança -Offsite Replication;Offsite Replication;Offsite Replication;Offsite Replication;Offsite Replication;Offsite Replication;Offsite Replication -Open Trusted Cloud;Open Trusted Cloud;Open Trusted Cloud;Open Trusted Cloud;Open Trusted Cloud;Open Trusted Cloud;Open Trusted Cloud -;;;Visibilité Pro;;Widoczna firma; -Discovery;Discovery;Discovery;Discovery;Discovery;Discovery;Discovery -Advance;Advance;Advance;Advance;Advance;Advance;Advance -DNSSEC;DNSSEC;DNSSEC;DNSSEC;DNSSEC;DNSSEC;DNSSEC -DDoS-Schutz;DDoS protection;DDoS Protection;Protection Anti-DDoS;Protezione anti-DDoS;Ochrona Anty-DDoS;Proteção DDoS -CDN Infrastructure;CDN Infrastructure;CDN Infrastructure;CDN Infrastructure;CDN Infrastructure;CDN Infrastructure;CDN Infrastructure -Metal Instance;Metal Instance;Metal Instance;Metal Instance;Metal Instance;Metal Instance;Metal Instance -Sicherheit von Hosts und Diensten (Hosted Private Cloud);Security for hosts and services (Hosted Private Cloud);Protección de hosts y servicios solo para Hosted Private Cloud;Sécurité des hôtes et services (Hosted Private Cloud);Sicurezza di host e servizi (Hosted Private Cloud);Bezpieczeństwo hostów i usług (Hosted Private Cloud);Segurança dos hosts e serviços (Hosted Private Cloud) -ML Serving;ML Serving;ML Serving;ML Serving;ML Serving;ML Serving;ML Serving -Data Platform;ForePaaS;Data Platform;Data Platform;Data Platform;Data Platform;Data Platform -;SMS;SMS;SMS;SMS;Usługa SMS; -Kimsufi;Kimsufi;Kimsufi;Kimsufi;Kimsufi;Kimsufi;Kimsufi -;Security for hosts and services;Protección de hosts y servicios;Sécurité des hôtes et services;Sicurezza di host e servizi;;Segurança dos hosts e serviços -Start SQL-Datenbanken;Start SQL Databases;Bases de datos Start SQL;Bases de données Start SQL;Database Start SQL;Bazy danych Start SQL;Bases de dados Start SQL -;Edge;;périphérie;;; -SSL-Zertifikat "Let's Encrypt";Let's Encrypt SSL certificate;Certificado SSL Let's Encrypt;Certificat SSL Let's Encrypt;Certificato SSL Let's Encrypt;Certyfikat SSL Let's Encrypt;Certificado SSL Let's Encrypt -Plesk Hosting (EOL);Plesk Hosting (EOL);Hosting Plesk (EOL);Hébergement Plesk (EOL);Hosting Plesk (EOL);Hosting Plesk (EOL);Alojamento Plesk (EOL) -Console Connect;Console Connect;Console Connect;Console Connect;Console Connect;Console Connect;Console Connect -Performance 2;Performance 2;Performance 2;Performance 2;Performance 2;Performance 2;Perf 2 -Microsoft 365;Microsoft 365;Microsoft 365;Microsoft 365;Microsoft 365;Microsoft 365;Microsoft 365 -;;;computer vision;;widzenie komputerowe; -;vRack Services;;;;vRack Services; -;;;Services et certifications;;Usługi i certyfikaty; -Kafka MirrorMaker;Kafka MirrorMaker;Kafka MirrorMaker;Kafka MirrorMaker;Kafka MirrorMaker;Kafka MirrorMaker;Kafka MirrorMaker -;;;Pack Nutanix Standard;;Pakiet Nutanix Standard; -OVHcloud Connect;OVHcloud Connect;OVHcloud Connect;OVHcloud Connect;OVHcloud Connect;OVHcloud Connect;OVHcloud Connect -Pro Hosting;Professional Hosting;Hosting Profesional;Hébergement Pro;Hosting Pro;Hosting Pro;Alojamento Pro -Storage;Storage;Storage;Storage;Storage;Storage;Storage -;Security;Seguridad;Sécurité;Sicurezza;Bezpieczeństwo;Segurança -Cloud Archive;Cloud Archive;Cloud Archive;Cloud Archive;Cloud Archive;Cloud Archive;Cloud Archive -SecNumCloud;SecNumCloud;SecNumCloud;SecNumCloud;SecNumCloud;SecNumCloud;SecNumCloud -;Data Analytics;Data Analytics;Data Analytics;Data Analytics;Data Analytics;Data Analytics -;;;Stockage et sauvegarde;;Przechowywanie i kopie zapasowe; -;decoupling;;découplage;;; -;Data localisation;;Localisation des données;;; -Eco Dedicated Server;Eco Dedicated Servers;Servidores dedicados Eco;Serveurs dédiés Eco;Server dedicati Eco;Serwery dedykowane Eco;Servidores dedicados Eco -Managed Rancher Service;Managed Rancher Service;Managed Rancher Service;Managed Rancher Service;Managed Rancher Service;Managed Rancher Service;Managed Rancher Service -;;;Offre Nutanix on OVHcloud packagée;;Oferta pakietowa Nutanix on OVHcloud; -High Performance Object Storage;High Performance Object Storage;High Performance Object Storage;High Performance Object Storage;High Performance Object Storage;High Performance Object Storage;High Performance Object Storage -;Service Endpoint;;;;Service Endpoint; -Bare Metal Cloud Netzwerkdienste;Network Services for Bare Metal Cloud;Servicios de red para Bare Metal Cloud;Services réseau Bare Metal Cloud;Servizi di rete Bare Metal Cloud;Usługi sieciowe Bare Metal Cloud;Serviços de rede Bare Metal Cloud -Cloud Web 2;Cloud Web 2;Cloud Web 2;Cloud Web 2;Cloud Web 2;Cloud Web 2;Cloud Web 2 -Billing Control;Billing Control;Billing Control;Billing control;Billing Control;Billing Control;Billing Control -HA-NAS;HA-NAS;NAS-HA;NAS-HA;NAS-HA;NAS-HA;NAS-HA -;graphical console;;console graphique;;; -Compute;Compute;Compute;Compute;Compute;Compute;Compute -Backup Storage;Backup Storage;Backup Storage;Backup Storage;Backup Storage;Backup Storage;Backup Storage -Managed Bare Metal;Managed Bare Metal;Managed Bare Metal;Managed Bare Metal;Managed Bare Metal;Managed Bare Metal;Managed Bare Metal -Cloud Web 3;Cloud Web 3;Cloud Web 3;Cloud Web 3;Cloud Web 3;Cloud Web 3;Cloud Web 3 -SSL-Zertifikat „Sectigo EV“;Sectigo EV SSL certificate;Certificado SSL Sectigo EV;Certificat SSL Sectigo EV;Certificato SSL Sectigo EV;Certyfikat SSL Sectigo EV;Certificado SSL Sectigo EV -OpenStack Orchestration;OpenStack Orchestration;OpenStack Orchestration;OpenStack Orchestration;OpenStack Orchestration;OpenStack Orchestration;OpenStack Orchestration -;Registrant;;Titulaire;;; -Block Storage;Block Storage;Block Storage;Block Storage;Block Storage;Block Storage;Block Storage -;reseller;;revendeur;;; -User and Role Management;User and Role Management;User and Role Management;User and role management;User and Role Management;User and Role Management;User and Role Management -;;;conditions générales de service;;Ogólne warunki świadczenia usługi; -;sub-processor;;sous-traitant ultérieur;;; -Professional Services;Professional Services;Professional Services;Professional Services;Professional Services;Professional Services;Professional Services -SSL Gateway;SSL Gateway;SSL Gateway;SSL Gateway;SSL Gateway;SSL Gateway;SSL Gateway -M3 Aggregator;M3 Aggregator;M3 Aggregator;M3 Aggregator;M3 Aggregator;M3 Aggregator;M3 Aggregator -;tape storage;;archivage sur bande;;; -VMware on OVHcloud;VMware on OVHcloud;VMware on OVHcloud;VMware on OVHcloud;VMware on OVHcloud;VMware on OVHcloud;VMware on OVHcloud -Private SQL-Datenbanken;Private SQL Databases;Bases de datos SQL Privado;Bases de données SQL Privé;Database SQL Privato;Bazy danych Private SQL;Bases de dados SQL Privado -Workflow Management;Workflow Management;Workflow Management;Workflow management;Workflow Management;Workflow Management;Workflow Management -;Databases;Databases;Databases;Database;Databases;Databases -Essential;Essential;Essential;Essential;Essential;Essential;Essential -High Speed Gen2 Block Storage;High Speed Gen2 Block Storage;High Speed Gen2;High Speed Gen2 Block Storage;High Speed Gen2;High Speed Gen2 Block Storage;High Speed Gen2 Block Storage -;Registry operators;;Registres opérateurs;;; -OVHcloud Startup Program;OVHcloud Startup Program;OVHcloud Startup Program;Startup program;OVHcloud Startup Program;OVHcloud Startup Program;OVHcloud Startup Program -Premium Support;Premium Support;Soporte Premium;Support Premium;Supporto Premium;Premium;Suporte Premium -;;;Public VCF as-a-Service;;Public VCF as a Service; -;;;Web Cloud;;Web Cloud; -Game DDoS-Schutz;Anti-DDoS Game;Anti-DDoS Game;Anti-DDoS Game;Anti-DDoS Game;Anty-DDoS Game;Anti-DDoS Game -NSX Edge-Dienste;NSX Edge Services;Servicios NSX Edge;Services NSX Edge;Servizi NSX Edge;NSX Edge Services;Serviços NSX Edge -;Containers and Orchestration;Containers & Orchestration;Containers and orchestration;Containers and Orchestration;Containers & Orchestration;Containers & Orchestration \ No newline at end of file From 16235f8b7f79e99179aa34d04cff9824c822928d Mon Sep 17 00:00:00 2001 From: Yoann Cosse Date: Fri, 24 Oct 2025 17:38:55 +0200 Subject: [PATCH 23/23] Deleting unneeded duplications --- .../create_balancing/guide.en-ie.md | 106 ------------------ .../create_balancing/guide.en-us.md | 106 ------------------ 2 files changed, 212 deletions(-) delete mode 100644 pages/network/load_balancer/create_balancing/guide.en-ie.md delete mode 100644 pages/network/load_balancer/create_balancing/guide.en-us.md diff --git a/pages/network/load_balancer/create_balancing/guide.en-ie.md b/pages/network/load_balancer/create_balancing/guide.en-ie.md deleted file mode 100644 index ddb51f2c8cf..00000000000 --- a/pages/network/load_balancer/create_balancing/guide.en-ie.md +++ /dev/null @@ -1,106 +0,0 @@ ---- -title: Load balancing methods -excerpt: Discover the various load balancing algorithms available with the OVHcloud Load Balancer -updated: 2025-10-24 ---- - -## Objective - -The OVHcloud Load Balancer service supports a variety of load balancing algorithms for your services. This setting dictates how the Load Balancer distributes incoming client requests among the servers in a farm. - -**This guide introduces the various load balancing methods and explains how to modify them.** - -## Requirements - -- An [OVHcloud Load Balancer](/links/network/load-balancer) service in your OVHcloud account. -- Access to the [OVHcloud Control Panel](/links/manager). -- You need to have created a server farm. - -## Instructions - -### Available Load Balancing Algorithms - -The load balancing setting is applied at the server farm level and defines the method by which client requests are distributed among the servers within that farm. - -For an overview of the OVHcloud Load Balancer service components, please refer to the [Load Balancer Introduction](/pages/network/load_balancer/use_presentation) guide. - -|Algorithm|Features| -|---|---| -|**First**|Directs the connection to the first available server based on its ID (smallest to largest).| -|**LeastConn**|Selects the server with the lowest number of active connections. This is recommended for long-duration sessions with light traffic. The *RoundRobin* algorithm is used for tie-breaking among equally loaded servers.| -|**RoundRobin**|Distributes connections sequentially, one after the other, for each new request. **This is the default algorithm.**| -|**Source**|Uses a hash of the source IP address to consistently redirect the same client IP to the same server, provided the server remains operational.| -|**URI**|Uses a hash of part or all of the URI path to consistently redirect identical URIs to the same server, provided the server remains operational. *(Applicable to HTTP/HTTPS farms only.)*| - -### Modify a server farm’s load balancing method via the OVHcloud Control Panel - -- In the `Server farms`{.action} section (1), locate the desired farm. You can edit it by clicking the three dots on the right-hand side (2), then on `Change`{.action}. - -![Modify a farm](images/server_cluster_change.png){.thumbnail} - -In `Advanced settings`{.action}, modify the `Load balancing method`{.action}. - -![Modify a farm](images/distrib_mode_edit.png){.thumbnail} - -Once your preferred method is selected, click `Update`{.action}, then click `Apply configuration`{.action} in the yellow banner that appears. - -![Apply configuration](images/apply_config.png){.thumbnail} - -### Modify a server farm’s load balancing method via the OVHcloud API - -The load balancing method is changed by updating the corresponding field within the server farm configuration. - -#### View details on a server farm - -Use this api call to view the details of a server farm given its ID. In this example, we work with an HTTP farm: - -> [!api] -> -> @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/http/farm/{farmId} -> - -|Setting|Meaning| -|---|---| -|serviceName*|Your Load Balancer service ID| -|farmId*|The farm’s ID number| - -|Response (BackendHttp)|Meaning| -|---|---| -|farmId|The farm’s ID number| -|balance|The load balancing algorithm currently set for the farm| -|zone|Name of the zone in which the farm is configured| -|port|Port used to contact the servers configured on the farm| -|probe|Type of probe currently configured on the farm| -|displayName|Name given to this farm| -|stickiness|Connection monitoring method currently set for the farm| - -#### Modify a server farm’s load balancing method - -Use this api call to edit the settings of a server farm given its ID. In this example, we work with an HTTP farm. To modify the balancing method, update the `BackendHttp.balance` field with an available algorithm: - -> [!api] -> -> @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/http/farm/{id} -> - -|Setting|Meaning| -|---|---| -|serviceName*|Your Load Balancer service ID| -|farmId*|The farm’s ID number| -|BackendHttp.balance|Preferred balancing method for this farm| - -#### Apply the modifications - -> [!api] -> -> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh -> - -|Setting|Meaning| -|---|---| -|serviceName*|Your Load Balancer service ID| -|zone*|Name of the zone in which to deploy the configuration| - -## Go further - -Join our [community of users](/links/community). \ No newline at end of file diff --git a/pages/network/load_balancer/create_balancing/guide.en-us.md b/pages/network/load_balancer/create_balancing/guide.en-us.md deleted file mode 100644 index ddb51f2c8cf..00000000000 --- a/pages/network/load_balancer/create_balancing/guide.en-us.md +++ /dev/null @@ -1,106 +0,0 @@ ---- -title: Load balancing methods -excerpt: Discover the various load balancing algorithms available with the OVHcloud Load Balancer -updated: 2025-10-24 ---- - -## Objective - -The OVHcloud Load Balancer service supports a variety of load balancing algorithms for your services. This setting dictates how the Load Balancer distributes incoming client requests among the servers in a farm. - -**This guide introduces the various load balancing methods and explains how to modify them.** - -## Requirements - -- An [OVHcloud Load Balancer](/links/network/load-balancer) service in your OVHcloud account. -- Access to the [OVHcloud Control Panel](/links/manager). -- You need to have created a server farm. - -## Instructions - -### Available Load Balancing Algorithms - -The load balancing setting is applied at the server farm level and defines the method by which client requests are distributed among the servers within that farm. - -For an overview of the OVHcloud Load Balancer service components, please refer to the [Load Balancer Introduction](/pages/network/load_balancer/use_presentation) guide. - -|Algorithm|Features| -|---|---| -|**First**|Directs the connection to the first available server based on its ID (smallest to largest).| -|**LeastConn**|Selects the server with the lowest number of active connections. This is recommended for long-duration sessions with light traffic. The *RoundRobin* algorithm is used for tie-breaking among equally loaded servers.| -|**RoundRobin**|Distributes connections sequentially, one after the other, for each new request. **This is the default algorithm.**| -|**Source**|Uses a hash of the source IP address to consistently redirect the same client IP to the same server, provided the server remains operational.| -|**URI**|Uses a hash of part or all of the URI path to consistently redirect identical URIs to the same server, provided the server remains operational. *(Applicable to HTTP/HTTPS farms only.)*| - -### Modify a server farm’s load balancing method via the OVHcloud Control Panel - -- In the `Server farms`{.action} section (1), locate the desired farm. You can edit it by clicking the three dots on the right-hand side (2), then on `Change`{.action}. - -![Modify a farm](images/server_cluster_change.png){.thumbnail} - -In `Advanced settings`{.action}, modify the `Load balancing method`{.action}. - -![Modify a farm](images/distrib_mode_edit.png){.thumbnail} - -Once your preferred method is selected, click `Update`{.action}, then click `Apply configuration`{.action} in the yellow banner that appears. - -![Apply configuration](images/apply_config.png){.thumbnail} - -### Modify a server farm’s load balancing method via the OVHcloud API - -The load balancing method is changed by updating the corresponding field within the server farm configuration. - -#### View details on a server farm - -Use this api call to view the details of a server farm given its ID. In this example, we work with an HTTP farm: - -> [!api] -> -> @api {v1} /ipLoadbalancing GET /ipLoadbalancing/{serviceName}/http/farm/{farmId} -> - -|Setting|Meaning| -|---|---| -|serviceName*|Your Load Balancer service ID| -|farmId*|The farm’s ID number| - -|Response (BackendHttp)|Meaning| -|---|---| -|farmId|The farm’s ID number| -|balance|The load balancing algorithm currently set for the farm| -|zone|Name of the zone in which the farm is configured| -|port|Port used to contact the servers configured on the farm| -|probe|Type of probe currently configured on the farm| -|displayName|Name given to this farm| -|stickiness|Connection monitoring method currently set for the farm| - -#### Modify a server farm’s load balancing method - -Use this api call to edit the settings of a server farm given its ID. In this example, we work with an HTTP farm. To modify the balancing method, update the `BackendHttp.balance` field with an available algorithm: - -> [!api] -> -> @api {v1} /ipLoadbalancing PUT /ipLoadbalancing/{serviceName}/http/farm/{id} -> - -|Setting|Meaning| -|---|---| -|serviceName*|Your Load Balancer service ID| -|farmId*|The farm’s ID number| -|BackendHttp.balance|Preferred balancing method for this farm| - -#### Apply the modifications - -> [!api] -> -> @api {v1} /ipLoadbalancing POST /ipLoadbalancing/{serviceName}/refresh -> - -|Setting|Meaning| -|---|---| -|serviceName*|Your Load Balancer service ID| -|zone*|Name of the zone in which to deploy the configuration| - -## Go further - -Join our [community of users](/links/community). \ No newline at end of file