update guides

Author: jfankam

pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.de-de.md

@@ -36,74 +36,64 @@ Our Public Cloud Load Balancer  is based on [OpenStack Octavia](https://wiki.ope
 
 ### Creating the Load Balancer from the OVHcloud Control Panel
 
-/// details | Unfold this section
+Open your Public Cloud project and click `Load Balancer`{.action} (under `Network`) in the left menu, then click the `Create a Load Balancer`{.action} button.
 
-> [!success]
-> Click on the tabs below to view each of the 6 steps in turn.
-
-> [!tabs]
->>
->> Open your Public Cloud project and click `Load Balancer`{.action} (under `Network`) in the left menu, then click the `Create a Load Balancer`{.action} button.
->>
->> The configuration page will open.
->>
-> **Step 1 : Size choice**
->>
->> ![Size choice](images/size.png){.thumbnail}
->>
->> The interface contains a link to the website on which the characteristics / benchmark of all size are provided. Once you have chosen your size, click `Next`{.action}.
->>
->>
-> **Step 2 : Region choice**
->>
->> ![Region choice](images/region.png){.thumbnail}
->>
->> Only regions on which you have a private network and at least one subnet can be selected. Select the region and click `Next`{.action}.
->>
-> **Step 3 : Attach a public IP (or not)**
->>
->> ![Public IP choice](images/floating_IP.png){.thumbnail}
->>
->> At this stage, you need to know if your Load Balancer will be receiving public traffic or not (for more details, read our [Public Cloud Networking concepts](/pages/public_cloud/public_cloud_network_services/concepts-01-public-cloud-networking-concepts) page). 
->>
->>
->> If your Load Balancer is processing public traffic, you have 2 options :
->>
->> - `New Public IP`: this option will create a new Floating IP for your Load Balancer. 
->> - If you already have a Floating IP, the interface will offer you to pick one.
->>
->> If your Load Balancer is processing private traffic, choose `No Public IP`.
->>
-> **Step 4 : Select the private network and the subnet where the Load Balancer will be spawned**
->>
->> ![Network choice](images/private_network.png){.thumbnail}
->>
->> The interface will inform you if the private network / subnet is not compliant with the prerequisites (see [Public Cloud Networking concepts](/pages/public_cloud/public_cloud_network_services/concepts-03-loadbalancer#network-prerequisites)).
->>
-> **Step 5 (optional) : Define the listener(s) and the members**
->>
->> ![Listener choice](images/listener.png){.thumbnail}
->>
->> - First, choose the listener protocol & the port according to the traffic you will receive. Note that a specific listener called `Prometheus` is available to monitor your Load Balancer. In that case, it is not possible to add members. For more information on this listener, read [this page](/pages/public_cloud/public_cloud_network_services/technical-resources-02-octavia-monitoring-prometheus).
->> - Then, choose the Health Monitor type. Note that since some health monitor types are not compatible with some protocols, the user interface filters those types so that you can only choose compatible items. For more information on the health monitor compatibility, read [this page](/pages/public_cloud/public_cloud_network_services/concepts-01-public-cloud-networking-concepts).
->> - Finally, from the instances of your region, choose the member IP & port that will be part of the pool. Note that in order to simplify the configuration workflow, it is only possible to have a pool with the same protocol as the listener, and that the member can only be chosen from the instance. Those limitations can be bypassed by skipping this part of configuration and use the pool / member configuration once the Load Balancer is created. 
->>
->>
->> > [!primary]
->> > In order to simplify the Load Balancer configuration workflow, it is only possible to have a pool with the same protocol as the listener and the member can only be chosen from the instance. Furthermore the pool load balancing algorithm is by default set to `ROUND_ROBIN`.
->> > Those limitations can be bypassed by skipping this part of configuration and use the pool / member configuration once the Load Balancer is created. 
->> >
->>
-> **Step 6 Define the name of Load Balancer**
->>
->> ![Name](images/name.png){.thumbnail}
->>
->> You can update the name according to your choice and click on `Create a Load Balancer`{.action}.
->>
->> You will be redirected to the Load Balancer listing page. Among the attributes that are displayed, the `Operating status` and `Provisioning status` provide information on the state of your load balancer. Find more information on the [Load Balancer concepts page](/pages/public_cloud/public_cloud_network_services/concepts-03-loadbalancer#operating-provisioning-status).
->> 
+The configuration page will open.
+
+#### Step 1: Size choice
+
+![Size choice](images/size.png){.thumbnail}
+
+The interface contains a link to the website on which the characteristics / benchmark of all size are provided. Once you have chosen your size, click `Next`{.action}.
+
+#### Step 2: Region choice
+
+![Region choice](images/region.png){.thumbnail}
+
+Only regions on which you have a private network and at least one subnet can be selected. Select the region and click `Next`{.action}.
+
+#### Step 3: Attach a public IP (or not)
+
+![Public IP choice](images/floating_IP.png){.thumbnail}
+
+At this stage, you need to know if your Load Balancer will be receiving public traffic or not (for more details, read our [Public Cloud Networking concepts](/pages/public_cloud/public_cloud_network_services/concepts-01-public-cloud-networking-concepts) page). 
+
+
+If your Load Balancer is processing public traffic, you have 2 options :
+
+- `New Public IP`: this option will create a new Floating IP for your Load Balancer. 
+- If you already have a Floating IP, the interface will offer you to pick one.
+
+If your Load Balancer is processing private traffic, choose `No Public IP`.
+
+#### Step 4: Select the private network and the subnet where the Load Balancer will be spawned
+
+![Network choice](images/private_network.png){.thumbnail}
+
+The interface will inform you if the private network / subnet is not compliant with the prerequisites (see [Public Cloud Networking concepts](/pages/public_cloud/public_cloud_network_services/concepts-03-loadbalancer#network-prerequisites)).
+
+#### Step 5 (optional): Define the listener(s) and the members
+
+![Listener choice](images/listener.png){.thumbnail}
+
+- First, choose the listener protocol & the port according to the traffic you will receive. Note that a specific listener called `Prometheus` is available to monitor your Load Balancer. In that case, it is not possible to add members. For more information on this listener, read [this page](/pages/public_cloud/public_cloud_network_services/technical-resources-02-octavia-monitoring-prometheus).
+- Then, choose the Health Monitor type. Note that since some health monitor types are not compatible with some protocols, the user interface filters those types so that you can only choose compatible items. For more information on the health monitor compatibility, read [this page](/pages/public_cloud/public_cloud_network_services/concepts-01-public-cloud-networking-concepts).
+- Finally, from the instances of your region, choose the member IP & port that will be part of the pool. Note that in order to simplify the configuration workflow, it is only possible to have a pool with the same protocol as the listener, and that the member can only be chosen from the instance. Those limitations can be bypassed by skipping this part of configuration and use the pool / member configuration once the Load Balancer is created. 
+
+
+> [!primary]
+> In order to simplify the Load Balancer configuration workflow, it is only possible to have a pool with the same protocol as the listener and the member can only be chosen from the instance. Furthermore the pool load balancing algorithm is by default set to `ROUND_ROBIN`.
+> Those limitations can be bypassed by skipping this part of configuration and use the pool / member configuration once the Load Balancer is created. 
+>
+
+#### Step 6: Define the name of Load Balancer
+
+![Name](images/name.png){.thumbnail}
+
+You can update the name according to your choice and click on `Create a Load Balancer`{.action}.
+
+You will be redirected to the Load Balancer listing page. Among the attributes that are displayed, the `Operating status` and `Provisioning status` provide information on the state of your load balancer. Find more information on the [Load Balancer concepts page](/pages/public_cloud/public_cloud_network_services/concepts-03-loadbalancer#operating-provisioning-status).
 
-///
 
 ### Creating the Load Balancer from the Openstack Command Line Interface
 

pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.en-asia.md

@@ -36,74 +36,63 @@ Our Public Cloud Load Balancer  is based on [OpenStack Octavia](https://wiki.ope
 
 ### Creating the Load Balancer from the OVHcloud Control Panel
 
-/// details | Unfold this section
+Open your Public Cloud project and click `Load Balancer`{.action} (under `Network`) in the left menu, then click the `Create a Load Balancer`{.action} button.
 
-> [!success]
-> Click on the tabs below to view each of the 6 steps in turn.
-
-> [!tabs]
->>
->> Open your Public Cloud project and click `Load Balancer`{.action} (under `Network`) in the left menu, then click the `Create a Load Balancer`{.action} button.
->>
->> The configuration page will open.
->>
-> **Step 1 : Size choice**
->>
->> ![Size choice](images/size.png){.thumbnail}
->>
->> The interface contains a link to the website on which the characteristics / benchmark of all size are provided. Once you have chosen your size, click `Next`{.action}.
->>
->>
-> **Step 2 : Region choice**
->>
->> ![Region choice](images/region.png){.thumbnail}
->>
->> Only regions on which you have a private network and at least one subnet can be selected. Select the region and click `Next`{.action}.
->>
-> **Step 3 : Attach a public IP (or not)**
->>
->> ![Public IP choice](images/floating_IP.png){.thumbnail}
->>
->> At this stage, you need to know if your Load Balancer will be receiving public traffic or not (for more details, read our [Public Cloud Networking concepts](/pages/public_cloud/public_cloud_network_services/concepts-01-public-cloud-networking-concepts) page). 
->>
->>
->> If your Load Balancer is processing public traffic, you have 2 options :
->>
->> - `New Public IP`: this option will create a new Floating IP for your Load Balancer. 
->> - If you already have a Floating IP, the interface will offer you to pick one.
->>
->> If your Load Balancer is processing private traffic, choose `No Public IP`.
->>
-> **Step 4 : Select the private network and the subnet where the Load Balancer will be spawned**
->>
->> ![Network choice](images/private_network.png){.thumbnail}
->>
->> The interface will inform you if the private network / subnet is not compliant with the prerequisites (see [Public Cloud Networking concepts](/pages/public_cloud/public_cloud_network_services/concepts-03-loadbalancer#network-prerequisites)).
->>
-> **Step 5 (optional) : Define the listener(s) and the members**
->>
->> ![Listener choice](images/listener.png){.thumbnail}
->>
->> - First, choose the listener protocol & the port according to the traffic you will receive. Note that a specific listener called `Prometheus` is available to monitor your Load Balancer. In that case, it is not possible to add members. For more information on this listener, read [this page](/pages/public_cloud/public_cloud_network_services/technical-resources-02-octavia-monitoring-prometheus).
->> - Then, choose the Health Monitor type. Note that since some health monitor types are not compatible with some protocols, the user interface filters those types so that you can only choose compatible items. For more information on the health monitor compatibility, read [this page](/pages/public_cloud/public_cloud_network_services/concepts-01-public-cloud-networking-concepts).
->> - Finally, from the instances of your region, choose the member IP & port that will be part of the pool. Note that in order to simplify the configuration workflow, it is only possible to have a pool with the same protocol as the listener, and that the member can only be chosen from the instance. Those limitations can be bypassed by skipping this part of configuration and use the pool / member configuration once the Load Balancer is created. 
->>
->>
->> > [!primary]
->> > In order to simplify the Load Balancer configuration workflow, it is only possible to have a pool with the same protocol as the listener and the member can only be chosen from the instance. Furthermore the pool load balancing algorithm is by default set to `ROUND_ROBIN`.
->> > Those limitations can be bypassed by skipping this part of configuration and use the pool / member configuration once the Load Balancer is created. 
->> >
->>
-> **Step 6 Define the name of Load Balancer**
->>
->> ![Name](images/name.png){.thumbnail}
->>
->> You can update the name according to your choice and click on `Create a Load Balancer`{.action}.
->>
->> You will be redirected to the Load Balancer listing page. Among the attributes that are displayed, the `Operating status` and `Provisioning status` provide information on the state of your load balancer. Find more information on the [Load Balancer concepts page](/pages/public_cloud/public_cloud_network_services/concepts-03-loadbalancer#operating-provisioning-status).
->> 
+The configuration page will open.
 
-///
+#### Step 1: Size choice
+
+![Size choice](images/size.png){.thumbnail}
+
+The interface contains a link to the website on which the characteristics / benchmark of all size are provided. Once you have chosen your size, click `Next`{.action}.
+
+#### Step 2: Region choice
+
+![Region choice](images/region.png){.thumbnail}
+
+Only regions on which you have a private network and at least one subnet can be selected. Select the region and click `Next`{.action}.
+
+#### Step 3: Attach a public IP (or not)
+
+![Public IP choice](images/floating_IP.png){.thumbnail}
+
+At this stage, you need to know if your Load Balancer will be receiving public traffic or not (for more details, read our [Public Cloud Networking concepts](/pages/public_cloud/public_cloud_network_services/concepts-01-public-cloud-networking-concepts) page). 
+
+
+If your Load Balancer is processing public traffic, you have 2 options :
+
+- `New Public IP`: this option will create a new Floating IP for your Load Balancer. 
+- If you already have a Floating IP, the interface will offer you to pick one.
+
+If your Load Balancer is processing private traffic, choose `No Public IP`.
+
+#### Step 4: Select the private network and the subnet where the Load Balancer will be spawned
+
+![Network choice](images/private_network.png){.thumbnail}
+
+The interface will inform you if the private network / subnet is not compliant with the prerequisites (see [Public Cloud Networking concepts](/pages/public_cloud/public_cloud_network_services/concepts-03-loadbalancer#network-prerequisites)).
+
+#### Step 5 (optional): Define the listener(s) and the members
+
+![Listener choice](images/listener.png){.thumbnail}
+
+- First, choose the listener protocol & the port according to the traffic you will receive. Note that a specific listener called `Prometheus` is available to monitor your Load Balancer. In that case, it is not possible to add members. For more information on this listener, read [this page](/pages/public_cloud/public_cloud_network_services/technical-resources-02-octavia-monitoring-prometheus).
+- Then, choose the Health Monitor type. Note that since some health monitor types are not compatible with some protocols, the user interface filters those types so that you can only choose compatible items. For more information on the health monitor compatibility, read [this page](/pages/public_cloud/public_cloud_network_services/concepts-01-public-cloud-networking-concepts).
+- Finally, from the instances of your region, choose the member IP & port that will be part of the pool. Note that in order to simplify the configuration workflow, it is only possible to have a pool with the same protocol as the listener, and that the member can only be chosen from the instance. Those limitations can be bypassed by skipping this part of configuration and use the pool / member configuration once the Load Balancer is created. 
+
+
+> [!primary]
+> In order to simplify the Load Balancer configuration workflow, it is only possible to have a pool with the same protocol as the listener and the member can only be chosen from the instance. Furthermore the pool load balancing algorithm is by default set to `ROUND_ROBIN`.
+> Those limitations can be bypassed by skipping this part of configuration and use the pool / member configuration once the Load Balancer is created. 
+>
+
+#### Step 6: Define the name of Load Balancer
+
+![Name](images/name.png){.thumbnail}
+
+You can update the name according to your choice and click on `Create a Load Balancer`{.action}.
+
+You will be redirected to the Load Balancer listing page. Among the attributes that are displayed, the `Operating status` and `Provisioning status` provide information on the state of your load balancer. Find more information on the [Load Balancer concepts page](/pages/public_cloud/public_cloud_network_services/concepts-03-loadbalancer#operating-provisioning-status).
 
 ### Creating the Load Balancer from the Openstack Command Line Interface