IPLB Refresh - Batch 3

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'
-updated: 2019-02-25
+excerpt: 'This guide will show you how to deploy a blue-green infrastructure with the OVHcloud Load Balancer'
+updated: 2025-10-17
 ---
 
 ## 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).