diff --git a/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.de-de.md b/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.de-de.md index 6a2c4a7c9ca..1fa20d549eb 100644 --- a/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.de-de.md +++ b/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.de-de.md @@ -1,23 +1,9 @@ --- -title: Getting started with Load Balancer on Public Cloud (EN) +title: Getting started with Load Balancer on Public Cloud excerpt: Discover how to launch a Load Balancer on Public Cloud -updated: 2025-04-28 +updated: 2025-11-03 --- - - ## Objective Our Public Cloud Load Balancer is based on [OpenStack Octavia](https://wiki.openstack.org/wiki/Octavia) and is fully integrated into the Public Cloud universe. @@ -34,153 +20,156 @@ Our Public Cloud Load Balancer is based on [OpenStack Octavia](https://wiki.ope ## Instructions -### Creating the Load Balancer from the OVHcloud Control Panel - -Log in to the [OVHcloud Control Panel](/links/manager), go to the `Public Cloud`{.action} section and select the Public Cloud project concerned. 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). - - -### Creating the Load Balancer from the Openstack Command Line Interface - -/// details | Unfold this section - -Another way to create a Load Balancer is through the Openstack Command Line Interface. Before you begin, consult the following guides: - -[Preparing an environment for using the OpenStack API](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api).
-[Setting OpenStack environment variables](/pages/public_cloud/public_cloud_cross_functional/loading_openstack_environment_variables). - -#### Configuring your private network - -Before creating a Load Balancer, you will need to set up a private network: - -```bash -openstack network create my_network - -openstack subnet create my_subnet --subnet-range --network my_network --no-dhcp - -openstack router create my_router - -openstack router add subnet my_router my_subnet - -openstack router set --external-gateway Ext-Net my_router -``` - -You can now attach your instances to the new network. We recommend following our guide to [integrate an instance into vRack](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#instance-integration). List the addresses of your instances in your network with the following command: - -```bash -openstack server list -``` - -In the next step, configure the network interfaces of your instances according to this output. - -#### Creating the Load Balancer - -You can view a list of the different Load Balancer flavors we offer with this command: - -```bash -openstack loadbalancer flavor list -``` - -You can now create your Load Balancer with the following command. In this example, we will create a "Small" Load Balancer. - -```bash -openstack loadbalancer create --name my_load_balancer --flavor small --vip-subnet-id my_subnet -``` - -Your Load Balancer will be configured with an IP address of the private network. If you want to have access from the internet, you will need to attach a Floating IP address. - -#### Attaching a Floating IP address to a Load Balancer - -This is how to attach a Floating IP address to a Load Balancer: - -```bash -openstack floating ip create Ext-Net -openstack floating ip set --port -``` - -> [!primary] -> -> To retrieve the VIP port ID of your Load Balancer, use `openstack loadbalancer show my_load_balancer`. - -#### Configuring your Load Balancer - -In this example we will configure an HTTP Load Balancer. In order to listen on port 80 of the Load Balancer, create a Listener with this command: - -```bash -openstack loadbalancer listener create --name my_listener_http --protocol HTTP --protocol-port 80 my_loadbalancer -``` - -Once the Listener has been created, you need to add each instance that can respond to external requests. To do this, you must create an Instance Pool: - -```bash -openstack loadbalancer pool create --name my_pool_http --lb-algorithm ROUND_ROBIN --listener my_listener --protocol HTTP -``` - -Add your instances to the Instance Pool: - -```bash -openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool -openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool -``` - -You can now access your Load Balancer via the Floating IP or private IP address from an instance in your private network. - -/// +### Creating the Load Balancer + +> [!tabs] +> Via the OVHcloud Control Panel +>> Log in to the [OVHcloud Control Panel](/links/manager), go to the `Public Cloud`{.action} section and select the Public Cloud project concerned. 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: Region choice** +>> +>> ![Region choice](images/region.png){.thumbnail} +>> +>> 1. **Select the zone type:** +>> +>> - 1AZ: Deployment in a single availability zone. +>> - 3AZ: Deployment spread across three availability zones for high availability. +>> +>> 2. **Choose the region:** Only regions where you have a private network and at least one subnet can be selected. Select the region and click `Next`{.action}. +>> +>> **Step 2: 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 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`{.action}. +>> +>> **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](/pages/public_cloud/public_cloud_network_services/concepts-03-loadbalancer#operating-provisioning-status)" page. +>> +> Via the OpenStack CLI +>> Another way to create a Load Balancer is through the OpenStack Command Line Interface. Before you begin, consult the following guides: +>> +>> - [Preparing an environment for using the OpenStack API](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api). +>> - [Setting OpenStack environment variables](/pages/public_cloud/public_cloud_cross_functional/loading_openstack_environment_variables). +>> +>> **Configuring your private network** +>> +>> Before creating a Load Balancer, you will need to set up a private network: +>> +>> ```bash +>> openstack network create my_network +>> +>> openstack subnet create my_subnet --subnet-range --network my_network --no-dhcp +>> +>> openstack router create my_router +>> +>> openstack router add subnet my_router my_subnet +>> +>> openstack router set --external-gateway Ext-Net my_router +>> ``` +>> +>> You can now attach your instances to the new network. We recommend following our guide to [integrate an instance into vRack](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#instance-integration). +>> +>> List the addresses of your instances in your network with the following command: +>> +>> ```bash +>> openstack server list +>> ``` +>> +>> In the next step, configure the network interfaces of your instances according to this output. +>> +>> **Creating the Load Balancer** +>> +>> You can view a list of the different Load Balancer flavors we offer with this command: +>> +>> ```bash +>> openstack loadbalancer flavor list +>> ``` +>> +>> You can now create your Load Balancer with the following command. In this example, we will create a "Small" Load Balancer. +>> +>> ```bash +>> openstack loadbalancer create --name my_load_balancer --flavor small --vip-subnet-id my_subnet +>> ``` +>> +>> Your Load Balancer will be configured with an IP address of the private network. If you want to have access from the internet, you will need to attach a Floating IP address. +>> +>> **Attaching a Floating IP address to a Load Balancer** +>> +>> This is how to attach a Floating IP address to a Load Balancer: +>> +>> ```bash +>> openstack floating ip create Ext-Net +>> openstack floating ip set --port +>> ``` +>> +>> > [!primary] +>> > +>> > To retrieve the VIP port ID of your Load Balancer, use `openstack loadbalancer show my_load_balancer`. +>> > +>> +>> **Configuring your Load Balancer** +>> +>> In this example we will configure an HTTP Load Balancer. In order to listen on port 80 of the Load Balancer, create a Listener with this command: +>> +>> ```bash +>> openstack loadbalancer listener create --name my_listener_http --protocol HTTP --protocol-port 80 my_loadbalancer +>> ``` +>> +>> Once the Listener has been created, you need to add each instance that can respond to external requests. To do this, you must create an Instance Pool: +>> +>> ```bash +>> openstack loadbalancer pool create --name my_pool_http --lb-algorithm ROUND_ROBIN --listener my_listener --protocol HTTP +>> ``` +>> +>> Add your instances to the Instance Pool: +>> +>> ```bash +>> openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool +>> openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool +>> ``` +>> +>> You can now access your Load Balancer via the Floating IP or private IP address from an instance in your private network. +>> ## Go further diff --git a/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.en-asia.md b/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.en-asia.md index eb8a711e9f4..1fa20d549eb 100644 --- a/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.en-asia.md +++ b/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.en-asia.md @@ -1,23 +1,9 @@ --- title: Getting started with Load Balancer on Public Cloud excerpt: Discover how to launch a Load Balancer on Public Cloud -updated: 2025-04-28 +updated: 2025-11-03 --- - - ## Objective Our Public Cloud Load Balancer is based on [OpenStack Octavia](https://wiki.openstack.org/wiki/Octavia) and is fully integrated into the Public Cloud universe. @@ -34,152 +20,156 @@ Our Public Cloud Load Balancer is based on [OpenStack Octavia](https://wiki.ope ## Instructions -### Creating the Load Balancer from the OVHcloud Control Panel - -Log in to the [OVHcloud Control Panel](/links/manager), go to the `Public Cloud`{.action} section and select the Public Cloud project concerned. 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). - -### Creating the Load Balancer from the Openstack Command Line Interface - -/// details | Unfold this section - -Another way to create a Load Balancer is through the Openstack Command Line Interface. Before you begin, consult the following guides: - -[Preparing an environment for using the OpenStack API](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api).
-[Setting OpenStack environment variables](/pages/public_cloud/public_cloud_cross_functional/loading_openstack_environment_variables). - -#### Configuring your private network - -Before creating a Load Balancer, you will need to set up a private network: - -```bash -openstack network create my_network - -openstack subnet create my_subnet --subnet-range --network my_network --no-dhcp - -openstack router create my_router - -openstack router add subnet my_router my_subnet - -openstack router set --external-gateway Ext-Net my_router -``` - -You can now attach your instances to the new network. We recommend following our guide to [integrate an instance into vRack](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#instance-integration). List the addresses of your instances in your network with the following command: - -```bash -openstack server list -``` - -In the next step, configure the network interfaces of your instances according to this output. - -#### Creating the Load Balancer - -You can view a list of the different Load Balancer flavors we offer with this command: - -```bash -openstack loadbalancer flavor list -``` - -You can now create your Load Balancer with the following command. In this example, we will create a "Small" Load Balancer. - -```bash -openstack loadbalancer create --name my_load_balancer --flavor small --vip-subnet-id my_subnet -``` - -Your Load Balancer will be configured with an IP address of the private network. If you want to have access from the internet, you will need to attach a Floating IP address. - -#### Attaching a Floating IP address to a Load Balancer - -This is how to attach a Floating IP address to a Load Balancer: - -```bash -openstack floating ip create Ext-Net -openstack floating ip set --port -``` - -> [!primary] -> -> To retrieve the VIP port ID of your Load Balancer, use `openstack loadbalancer show my_load_balancer`. - -#### Configuring your Load Balancer - -In this example we will configure an HTTP Load Balancer. In order to listen on port 80 of the Load Balancer, create a Listener with this command: - -```bash -openstack loadbalancer listener create --name my_listener_http --protocol HTTP --protocol-port 80 my_loadbalancer -``` - -Once the Listener has been created, you need to add each instance that can respond to external requests. To do this, you must create an Instance Pool: - -```bash -openstack loadbalancer pool create --name my_pool_http --lb-algorithm ROUND_ROBIN --listener my_listener --protocol HTTP -``` - -Add your instances to the Instance Pool: - -```bash -openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool -openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool -``` - -You can now access your Load Balancer via the Floating IP or private IP address from an instance in your private network. - -/// +### Creating the Load Balancer + +> [!tabs] +> Via the OVHcloud Control Panel +>> Log in to the [OVHcloud Control Panel](/links/manager), go to the `Public Cloud`{.action} section and select the Public Cloud project concerned. 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: Region choice** +>> +>> ![Region choice](images/region.png){.thumbnail} +>> +>> 1. **Select the zone type:** +>> +>> - 1AZ: Deployment in a single availability zone. +>> - 3AZ: Deployment spread across three availability zones for high availability. +>> +>> 2. **Choose the region:** Only regions where you have a private network and at least one subnet can be selected. Select the region and click `Next`{.action}. +>> +>> **Step 2: 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 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`{.action}. +>> +>> **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](/pages/public_cloud/public_cloud_network_services/concepts-03-loadbalancer#operating-provisioning-status)" page. +>> +> Via the OpenStack CLI +>> Another way to create a Load Balancer is through the OpenStack Command Line Interface. Before you begin, consult the following guides: +>> +>> - [Preparing an environment for using the OpenStack API](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api). +>> - [Setting OpenStack environment variables](/pages/public_cloud/public_cloud_cross_functional/loading_openstack_environment_variables). +>> +>> **Configuring your private network** +>> +>> Before creating a Load Balancer, you will need to set up a private network: +>> +>> ```bash +>> openstack network create my_network +>> +>> openstack subnet create my_subnet --subnet-range --network my_network --no-dhcp +>> +>> openstack router create my_router +>> +>> openstack router add subnet my_router my_subnet +>> +>> openstack router set --external-gateway Ext-Net my_router +>> ``` +>> +>> You can now attach your instances to the new network. We recommend following our guide to [integrate an instance into vRack](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#instance-integration). +>> +>> List the addresses of your instances in your network with the following command: +>> +>> ```bash +>> openstack server list +>> ``` +>> +>> In the next step, configure the network interfaces of your instances according to this output. +>> +>> **Creating the Load Balancer** +>> +>> You can view a list of the different Load Balancer flavors we offer with this command: +>> +>> ```bash +>> openstack loadbalancer flavor list +>> ``` +>> +>> You can now create your Load Balancer with the following command. In this example, we will create a "Small" Load Balancer. +>> +>> ```bash +>> openstack loadbalancer create --name my_load_balancer --flavor small --vip-subnet-id my_subnet +>> ``` +>> +>> Your Load Balancer will be configured with an IP address of the private network. If you want to have access from the internet, you will need to attach a Floating IP address. +>> +>> **Attaching a Floating IP address to a Load Balancer** +>> +>> This is how to attach a Floating IP address to a Load Balancer: +>> +>> ```bash +>> openstack floating ip create Ext-Net +>> openstack floating ip set --port +>> ``` +>> +>> > [!primary] +>> > +>> > To retrieve the VIP port ID of your Load Balancer, use `openstack loadbalancer show my_load_balancer`. +>> > +>> +>> **Configuring your Load Balancer** +>> +>> In this example we will configure an HTTP Load Balancer. In order to listen on port 80 of the Load Balancer, create a Listener with this command: +>> +>> ```bash +>> openstack loadbalancer listener create --name my_listener_http --protocol HTTP --protocol-port 80 my_loadbalancer +>> ``` +>> +>> Once the Listener has been created, you need to add each instance that can respond to external requests. To do this, you must create an Instance Pool: +>> +>> ```bash +>> openstack loadbalancer pool create --name my_pool_http --lb-algorithm ROUND_ROBIN --listener my_listener --protocol HTTP +>> ``` +>> +>> Add your instances to the Instance Pool: +>> +>> ```bash +>> openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool +>> openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool +>> ``` +>> +>> You can now access your Load Balancer via the Floating IP or private IP address from an instance in your private network. +>> ## Go further diff --git a/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.en-au.md b/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.en-au.md index eb8a711e9f4..1fa20d549eb 100644 --- a/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.en-au.md +++ b/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.en-au.md @@ -1,23 +1,9 @@ --- title: Getting started with Load Balancer on Public Cloud excerpt: Discover how to launch a Load Balancer on Public Cloud -updated: 2025-04-28 +updated: 2025-11-03 --- - - ## Objective Our Public Cloud Load Balancer is based on [OpenStack Octavia](https://wiki.openstack.org/wiki/Octavia) and is fully integrated into the Public Cloud universe. @@ -34,152 +20,156 @@ Our Public Cloud Load Balancer is based on [OpenStack Octavia](https://wiki.ope ## Instructions -### Creating the Load Balancer from the OVHcloud Control Panel - -Log in to the [OVHcloud Control Panel](/links/manager), go to the `Public Cloud`{.action} section and select the Public Cloud project concerned. 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). - -### Creating the Load Balancer from the Openstack Command Line Interface - -/// details | Unfold this section - -Another way to create a Load Balancer is through the Openstack Command Line Interface. Before you begin, consult the following guides: - -[Preparing an environment for using the OpenStack API](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api).
-[Setting OpenStack environment variables](/pages/public_cloud/public_cloud_cross_functional/loading_openstack_environment_variables). - -#### Configuring your private network - -Before creating a Load Balancer, you will need to set up a private network: - -```bash -openstack network create my_network - -openstack subnet create my_subnet --subnet-range --network my_network --no-dhcp - -openstack router create my_router - -openstack router add subnet my_router my_subnet - -openstack router set --external-gateway Ext-Net my_router -``` - -You can now attach your instances to the new network. We recommend following our guide to [integrate an instance into vRack](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#instance-integration). List the addresses of your instances in your network with the following command: - -```bash -openstack server list -``` - -In the next step, configure the network interfaces of your instances according to this output. - -#### Creating the Load Balancer - -You can view a list of the different Load Balancer flavors we offer with this command: - -```bash -openstack loadbalancer flavor list -``` - -You can now create your Load Balancer with the following command. In this example, we will create a "Small" Load Balancer. - -```bash -openstack loadbalancer create --name my_load_balancer --flavor small --vip-subnet-id my_subnet -``` - -Your Load Balancer will be configured with an IP address of the private network. If you want to have access from the internet, you will need to attach a Floating IP address. - -#### Attaching a Floating IP address to a Load Balancer - -This is how to attach a Floating IP address to a Load Balancer: - -```bash -openstack floating ip create Ext-Net -openstack floating ip set --port -``` - -> [!primary] -> -> To retrieve the VIP port ID of your Load Balancer, use `openstack loadbalancer show my_load_balancer`. - -#### Configuring your Load Balancer - -In this example we will configure an HTTP Load Balancer. In order to listen on port 80 of the Load Balancer, create a Listener with this command: - -```bash -openstack loadbalancer listener create --name my_listener_http --protocol HTTP --protocol-port 80 my_loadbalancer -``` - -Once the Listener has been created, you need to add each instance that can respond to external requests. To do this, you must create an Instance Pool: - -```bash -openstack loadbalancer pool create --name my_pool_http --lb-algorithm ROUND_ROBIN --listener my_listener --protocol HTTP -``` - -Add your instances to the Instance Pool: - -```bash -openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool -openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool -``` - -You can now access your Load Balancer via the Floating IP or private IP address from an instance in your private network. - -/// +### Creating the Load Balancer + +> [!tabs] +> Via the OVHcloud Control Panel +>> Log in to the [OVHcloud Control Panel](/links/manager), go to the `Public Cloud`{.action} section and select the Public Cloud project concerned. 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: Region choice** +>> +>> ![Region choice](images/region.png){.thumbnail} +>> +>> 1. **Select the zone type:** +>> +>> - 1AZ: Deployment in a single availability zone. +>> - 3AZ: Deployment spread across three availability zones for high availability. +>> +>> 2. **Choose the region:** Only regions where you have a private network and at least one subnet can be selected. Select the region and click `Next`{.action}. +>> +>> **Step 2: 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 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`{.action}. +>> +>> **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](/pages/public_cloud/public_cloud_network_services/concepts-03-loadbalancer#operating-provisioning-status)" page. +>> +> Via the OpenStack CLI +>> Another way to create a Load Balancer is through the OpenStack Command Line Interface. Before you begin, consult the following guides: +>> +>> - [Preparing an environment for using the OpenStack API](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api). +>> - [Setting OpenStack environment variables](/pages/public_cloud/public_cloud_cross_functional/loading_openstack_environment_variables). +>> +>> **Configuring your private network** +>> +>> Before creating a Load Balancer, you will need to set up a private network: +>> +>> ```bash +>> openstack network create my_network +>> +>> openstack subnet create my_subnet --subnet-range --network my_network --no-dhcp +>> +>> openstack router create my_router +>> +>> openstack router add subnet my_router my_subnet +>> +>> openstack router set --external-gateway Ext-Net my_router +>> ``` +>> +>> You can now attach your instances to the new network. We recommend following our guide to [integrate an instance into vRack](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#instance-integration). +>> +>> List the addresses of your instances in your network with the following command: +>> +>> ```bash +>> openstack server list +>> ``` +>> +>> In the next step, configure the network interfaces of your instances according to this output. +>> +>> **Creating the Load Balancer** +>> +>> You can view a list of the different Load Balancer flavors we offer with this command: +>> +>> ```bash +>> openstack loadbalancer flavor list +>> ``` +>> +>> You can now create your Load Balancer with the following command. In this example, we will create a "Small" Load Balancer. +>> +>> ```bash +>> openstack loadbalancer create --name my_load_balancer --flavor small --vip-subnet-id my_subnet +>> ``` +>> +>> Your Load Balancer will be configured with an IP address of the private network. If you want to have access from the internet, you will need to attach a Floating IP address. +>> +>> **Attaching a Floating IP address to a Load Balancer** +>> +>> This is how to attach a Floating IP address to a Load Balancer: +>> +>> ```bash +>> openstack floating ip create Ext-Net +>> openstack floating ip set --port +>> ``` +>> +>> > [!primary] +>> > +>> > To retrieve the VIP port ID of your Load Balancer, use `openstack loadbalancer show my_load_balancer`. +>> > +>> +>> **Configuring your Load Balancer** +>> +>> In this example we will configure an HTTP Load Balancer. In order to listen on port 80 of the Load Balancer, create a Listener with this command: +>> +>> ```bash +>> openstack loadbalancer listener create --name my_listener_http --protocol HTTP --protocol-port 80 my_loadbalancer +>> ``` +>> +>> Once the Listener has been created, you need to add each instance that can respond to external requests. To do this, you must create an Instance Pool: +>> +>> ```bash +>> openstack loadbalancer pool create --name my_pool_http --lb-algorithm ROUND_ROBIN --listener my_listener --protocol HTTP +>> ``` +>> +>> Add your instances to the Instance Pool: +>> +>> ```bash +>> openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool +>> openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool +>> ``` +>> +>> You can now access your Load Balancer via the Floating IP or private IP address from an instance in your private network. +>> ## Go further diff --git a/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.en-ca.md b/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.en-ca.md index eb8a711e9f4..1fa20d549eb 100644 --- a/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.en-ca.md +++ b/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.en-ca.md @@ -1,23 +1,9 @@ --- title: Getting started with Load Balancer on Public Cloud excerpt: Discover how to launch a Load Balancer on Public Cloud -updated: 2025-04-28 +updated: 2025-11-03 --- - - ## Objective Our Public Cloud Load Balancer is based on [OpenStack Octavia](https://wiki.openstack.org/wiki/Octavia) and is fully integrated into the Public Cloud universe. @@ -34,152 +20,156 @@ Our Public Cloud Load Balancer is based on [OpenStack Octavia](https://wiki.ope ## Instructions -### Creating the Load Balancer from the OVHcloud Control Panel - -Log in to the [OVHcloud Control Panel](/links/manager), go to the `Public Cloud`{.action} section and select the Public Cloud project concerned. 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). - -### Creating the Load Balancer from the Openstack Command Line Interface - -/// details | Unfold this section - -Another way to create a Load Balancer is through the Openstack Command Line Interface. Before you begin, consult the following guides: - -[Preparing an environment for using the OpenStack API](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api).
-[Setting OpenStack environment variables](/pages/public_cloud/public_cloud_cross_functional/loading_openstack_environment_variables). - -#### Configuring your private network - -Before creating a Load Balancer, you will need to set up a private network: - -```bash -openstack network create my_network - -openstack subnet create my_subnet --subnet-range --network my_network --no-dhcp - -openstack router create my_router - -openstack router add subnet my_router my_subnet - -openstack router set --external-gateway Ext-Net my_router -``` - -You can now attach your instances to the new network. We recommend following our guide to [integrate an instance into vRack](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#instance-integration). List the addresses of your instances in your network with the following command: - -```bash -openstack server list -``` - -In the next step, configure the network interfaces of your instances according to this output. - -#### Creating the Load Balancer - -You can view a list of the different Load Balancer flavors we offer with this command: - -```bash -openstack loadbalancer flavor list -``` - -You can now create your Load Balancer with the following command. In this example, we will create a "Small" Load Balancer. - -```bash -openstack loadbalancer create --name my_load_balancer --flavor small --vip-subnet-id my_subnet -``` - -Your Load Balancer will be configured with an IP address of the private network. If you want to have access from the internet, you will need to attach a Floating IP address. - -#### Attaching a Floating IP address to a Load Balancer - -This is how to attach a Floating IP address to a Load Balancer: - -```bash -openstack floating ip create Ext-Net -openstack floating ip set --port -``` - -> [!primary] -> -> To retrieve the VIP port ID of your Load Balancer, use `openstack loadbalancer show my_load_balancer`. - -#### Configuring your Load Balancer - -In this example we will configure an HTTP Load Balancer. In order to listen on port 80 of the Load Balancer, create a Listener with this command: - -```bash -openstack loadbalancer listener create --name my_listener_http --protocol HTTP --protocol-port 80 my_loadbalancer -``` - -Once the Listener has been created, you need to add each instance that can respond to external requests. To do this, you must create an Instance Pool: - -```bash -openstack loadbalancer pool create --name my_pool_http --lb-algorithm ROUND_ROBIN --listener my_listener --protocol HTTP -``` - -Add your instances to the Instance Pool: - -```bash -openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool -openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool -``` - -You can now access your Load Balancer via the Floating IP or private IP address from an instance in your private network. - -/// +### Creating the Load Balancer + +> [!tabs] +> Via the OVHcloud Control Panel +>> Log in to the [OVHcloud Control Panel](/links/manager), go to the `Public Cloud`{.action} section and select the Public Cloud project concerned. 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: Region choice** +>> +>> ![Region choice](images/region.png){.thumbnail} +>> +>> 1. **Select the zone type:** +>> +>> - 1AZ: Deployment in a single availability zone. +>> - 3AZ: Deployment spread across three availability zones for high availability. +>> +>> 2. **Choose the region:** Only regions where you have a private network and at least one subnet can be selected. Select the region and click `Next`{.action}. +>> +>> **Step 2: 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 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`{.action}. +>> +>> **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](/pages/public_cloud/public_cloud_network_services/concepts-03-loadbalancer#operating-provisioning-status)" page. +>> +> Via the OpenStack CLI +>> Another way to create a Load Balancer is through the OpenStack Command Line Interface. Before you begin, consult the following guides: +>> +>> - [Preparing an environment for using the OpenStack API](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api). +>> - [Setting OpenStack environment variables](/pages/public_cloud/public_cloud_cross_functional/loading_openstack_environment_variables). +>> +>> **Configuring your private network** +>> +>> Before creating a Load Balancer, you will need to set up a private network: +>> +>> ```bash +>> openstack network create my_network +>> +>> openstack subnet create my_subnet --subnet-range --network my_network --no-dhcp +>> +>> openstack router create my_router +>> +>> openstack router add subnet my_router my_subnet +>> +>> openstack router set --external-gateway Ext-Net my_router +>> ``` +>> +>> You can now attach your instances to the new network. We recommend following our guide to [integrate an instance into vRack](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#instance-integration). +>> +>> List the addresses of your instances in your network with the following command: +>> +>> ```bash +>> openstack server list +>> ``` +>> +>> In the next step, configure the network interfaces of your instances according to this output. +>> +>> **Creating the Load Balancer** +>> +>> You can view a list of the different Load Balancer flavors we offer with this command: +>> +>> ```bash +>> openstack loadbalancer flavor list +>> ``` +>> +>> You can now create your Load Balancer with the following command. In this example, we will create a "Small" Load Balancer. +>> +>> ```bash +>> openstack loadbalancer create --name my_load_balancer --flavor small --vip-subnet-id my_subnet +>> ``` +>> +>> Your Load Balancer will be configured with an IP address of the private network. If you want to have access from the internet, you will need to attach a Floating IP address. +>> +>> **Attaching a Floating IP address to a Load Balancer** +>> +>> This is how to attach a Floating IP address to a Load Balancer: +>> +>> ```bash +>> openstack floating ip create Ext-Net +>> openstack floating ip set --port +>> ``` +>> +>> > [!primary] +>> > +>> > To retrieve the VIP port ID of your Load Balancer, use `openstack loadbalancer show my_load_balancer`. +>> > +>> +>> **Configuring your Load Balancer** +>> +>> In this example we will configure an HTTP Load Balancer. In order to listen on port 80 of the Load Balancer, create a Listener with this command: +>> +>> ```bash +>> openstack loadbalancer listener create --name my_listener_http --protocol HTTP --protocol-port 80 my_loadbalancer +>> ``` +>> +>> Once the Listener has been created, you need to add each instance that can respond to external requests. To do this, you must create an Instance Pool: +>> +>> ```bash +>> openstack loadbalancer pool create --name my_pool_http --lb-algorithm ROUND_ROBIN --listener my_listener --protocol HTTP +>> ``` +>> +>> Add your instances to the Instance Pool: +>> +>> ```bash +>> openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool +>> openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool +>> ``` +>> +>> You can now access your Load Balancer via the Floating IP or private IP address from an instance in your private network. +>> ## Go further diff --git a/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.en-gb.md b/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.en-gb.md index eb8a711e9f4..1fa20d549eb 100644 --- a/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.en-gb.md +++ b/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.en-gb.md @@ -1,23 +1,9 @@ --- title: Getting started with Load Balancer on Public Cloud excerpt: Discover how to launch a Load Balancer on Public Cloud -updated: 2025-04-28 +updated: 2025-11-03 --- - - ## Objective Our Public Cloud Load Balancer is based on [OpenStack Octavia](https://wiki.openstack.org/wiki/Octavia) and is fully integrated into the Public Cloud universe. @@ -34,152 +20,156 @@ Our Public Cloud Load Balancer is based on [OpenStack Octavia](https://wiki.ope ## Instructions -### Creating the Load Balancer from the OVHcloud Control Panel - -Log in to the [OVHcloud Control Panel](/links/manager), go to the `Public Cloud`{.action} section and select the Public Cloud project concerned. 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). - -### Creating the Load Balancer from the Openstack Command Line Interface - -/// details | Unfold this section - -Another way to create a Load Balancer is through the Openstack Command Line Interface. Before you begin, consult the following guides: - -[Preparing an environment for using the OpenStack API](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api).
-[Setting OpenStack environment variables](/pages/public_cloud/public_cloud_cross_functional/loading_openstack_environment_variables). - -#### Configuring your private network - -Before creating a Load Balancer, you will need to set up a private network: - -```bash -openstack network create my_network - -openstack subnet create my_subnet --subnet-range --network my_network --no-dhcp - -openstack router create my_router - -openstack router add subnet my_router my_subnet - -openstack router set --external-gateway Ext-Net my_router -``` - -You can now attach your instances to the new network. We recommend following our guide to [integrate an instance into vRack](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#instance-integration). List the addresses of your instances in your network with the following command: - -```bash -openstack server list -``` - -In the next step, configure the network interfaces of your instances according to this output. - -#### Creating the Load Balancer - -You can view a list of the different Load Balancer flavors we offer with this command: - -```bash -openstack loadbalancer flavor list -``` - -You can now create your Load Balancer with the following command. In this example, we will create a "Small" Load Balancer. - -```bash -openstack loadbalancer create --name my_load_balancer --flavor small --vip-subnet-id my_subnet -``` - -Your Load Balancer will be configured with an IP address of the private network. If you want to have access from the internet, you will need to attach a Floating IP address. - -#### Attaching a Floating IP address to a Load Balancer - -This is how to attach a Floating IP address to a Load Balancer: - -```bash -openstack floating ip create Ext-Net -openstack floating ip set --port -``` - -> [!primary] -> -> To retrieve the VIP port ID of your Load Balancer, use `openstack loadbalancer show my_load_balancer`. - -#### Configuring your Load Balancer - -In this example we will configure an HTTP Load Balancer. In order to listen on port 80 of the Load Balancer, create a Listener with this command: - -```bash -openstack loadbalancer listener create --name my_listener_http --protocol HTTP --protocol-port 80 my_loadbalancer -``` - -Once the Listener has been created, you need to add each instance that can respond to external requests. To do this, you must create an Instance Pool: - -```bash -openstack loadbalancer pool create --name my_pool_http --lb-algorithm ROUND_ROBIN --listener my_listener --protocol HTTP -``` - -Add your instances to the Instance Pool: - -```bash -openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool -openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool -``` - -You can now access your Load Balancer via the Floating IP or private IP address from an instance in your private network. - -/// +### Creating the Load Balancer + +> [!tabs] +> Via the OVHcloud Control Panel +>> Log in to the [OVHcloud Control Panel](/links/manager), go to the `Public Cloud`{.action} section and select the Public Cloud project concerned. 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: Region choice** +>> +>> ![Region choice](images/region.png){.thumbnail} +>> +>> 1. **Select the zone type:** +>> +>> - 1AZ: Deployment in a single availability zone. +>> - 3AZ: Deployment spread across three availability zones for high availability. +>> +>> 2. **Choose the region:** Only regions where you have a private network and at least one subnet can be selected. Select the region and click `Next`{.action}. +>> +>> **Step 2: 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 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`{.action}. +>> +>> **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](/pages/public_cloud/public_cloud_network_services/concepts-03-loadbalancer#operating-provisioning-status)" page. +>> +> Via the OpenStack CLI +>> Another way to create a Load Balancer is through the OpenStack Command Line Interface. Before you begin, consult the following guides: +>> +>> - [Preparing an environment for using the OpenStack API](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api). +>> - [Setting OpenStack environment variables](/pages/public_cloud/public_cloud_cross_functional/loading_openstack_environment_variables). +>> +>> **Configuring your private network** +>> +>> Before creating a Load Balancer, you will need to set up a private network: +>> +>> ```bash +>> openstack network create my_network +>> +>> openstack subnet create my_subnet --subnet-range --network my_network --no-dhcp +>> +>> openstack router create my_router +>> +>> openstack router add subnet my_router my_subnet +>> +>> openstack router set --external-gateway Ext-Net my_router +>> ``` +>> +>> You can now attach your instances to the new network. We recommend following our guide to [integrate an instance into vRack](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#instance-integration). +>> +>> List the addresses of your instances in your network with the following command: +>> +>> ```bash +>> openstack server list +>> ``` +>> +>> In the next step, configure the network interfaces of your instances according to this output. +>> +>> **Creating the Load Balancer** +>> +>> You can view a list of the different Load Balancer flavors we offer with this command: +>> +>> ```bash +>> openstack loadbalancer flavor list +>> ``` +>> +>> You can now create your Load Balancer with the following command. In this example, we will create a "Small" Load Balancer. +>> +>> ```bash +>> openstack loadbalancer create --name my_load_balancer --flavor small --vip-subnet-id my_subnet +>> ``` +>> +>> Your Load Balancer will be configured with an IP address of the private network. If you want to have access from the internet, you will need to attach a Floating IP address. +>> +>> **Attaching a Floating IP address to a Load Balancer** +>> +>> This is how to attach a Floating IP address to a Load Balancer: +>> +>> ```bash +>> openstack floating ip create Ext-Net +>> openstack floating ip set --port +>> ``` +>> +>> > [!primary] +>> > +>> > To retrieve the VIP port ID of your Load Balancer, use `openstack loadbalancer show my_load_balancer`. +>> > +>> +>> **Configuring your Load Balancer** +>> +>> In this example we will configure an HTTP Load Balancer. In order to listen on port 80 of the Load Balancer, create a Listener with this command: +>> +>> ```bash +>> openstack loadbalancer listener create --name my_listener_http --protocol HTTP --protocol-port 80 my_loadbalancer +>> ``` +>> +>> Once the Listener has been created, you need to add each instance that can respond to external requests. To do this, you must create an Instance Pool: +>> +>> ```bash +>> openstack loadbalancer pool create --name my_pool_http --lb-algorithm ROUND_ROBIN --listener my_listener --protocol HTTP +>> ``` +>> +>> Add your instances to the Instance Pool: +>> +>> ```bash +>> openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool +>> openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool +>> ``` +>> +>> You can now access your Load Balancer via the Floating IP or private IP address from an instance in your private network. +>> ## Go further diff --git a/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.en-ie.md b/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.en-ie.md index eb8a711e9f4..1fa20d549eb 100644 --- a/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.en-ie.md +++ b/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.en-ie.md @@ -1,23 +1,9 @@ --- title: Getting started with Load Balancer on Public Cloud excerpt: Discover how to launch a Load Balancer on Public Cloud -updated: 2025-04-28 +updated: 2025-11-03 --- - - ## Objective Our Public Cloud Load Balancer is based on [OpenStack Octavia](https://wiki.openstack.org/wiki/Octavia) and is fully integrated into the Public Cloud universe. @@ -34,152 +20,156 @@ Our Public Cloud Load Balancer is based on [OpenStack Octavia](https://wiki.ope ## Instructions -### Creating the Load Balancer from the OVHcloud Control Panel - -Log in to the [OVHcloud Control Panel](/links/manager), go to the `Public Cloud`{.action} section and select the Public Cloud project concerned. 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). - -### Creating the Load Balancer from the Openstack Command Line Interface - -/// details | Unfold this section - -Another way to create a Load Balancer is through the Openstack Command Line Interface. Before you begin, consult the following guides: - -[Preparing an environment for using the OpenStack API](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api).
-[Setting OpenStack environment variables](/pages/public_cloud/public_cloud_cross_functional/loading_openstack_environment_variables). - -#### Configuring your private network - -Before creating a Load Balancer, you will need to set up a private network: - -```bash -openstack network create my_network - -openstack subnet create my_subnet --subnet-range --network my_network --no-dhcp - -openstack router create my_router - -openstack router add subnet my_router my_subnet - -openstack router set --external-gateway Ext-Net my_router -``` - -You can now attach your instances to the new network. We recommend following our guide to [integrate an instance into vRack](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#instance-integration). List the addresses of your instances in your network with the following command: - -```bash -openstack server list -``` - -In the next step, configure the network interfaces of your instances according to this output. - -#### Creating the Load Balancer - -You can view a list of the different Load Balancer flavors we offer with this command: - -```bash -openstack loadbalancer flavor list -``` - -You can now create your Load Balancer with the following command. In this example, we will create a "Small" Load Balancer. - -```bash -openstack loadbalancer create --name my_load_balancer --flavor small --vip-subnet-id my_subnet -``` - -Your Load Balancer will be configured with an IP address of the private network. If you want to have access from the internet, you will need to attach a Floating IP address. - -#### Attaching a Floating IP address to a Load Balancer - -This is how to attach a Floating IP address to a Load Balancer: - -```bash -openstack floating ip create Ext-Net -openstack floating ip set --port -``` - -> [!primary] -> -> To retrieve the VIP port ID of your Load Balancer, use `openstack loadbalancer show my_load_balancer`. - -#### Configuring your Load Balancer - -In this example we will configure an HTTP Load Balancer. In order to listen on port 80 of the Load Balancer, create a Listener with this command: - -```bash -openstack loadbalancer listener create --name my_listener_http --protocol HTTP --protocol-port 80 my_loadbalancer -``` - -Once the Listener has been created, you need to add each instance that can respond to external requests. To do this, you must create an Instance Pool: - -```bash -openstack loadbalancer pool create --name my_pool_http --lb-algorithm ROUND_ROBIN --listener my_listener --protocol HTTP -``` - -Add your instances to the Instance Pool: - -```bash -openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool -openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool -``` - -You can now access your Load Balancer via the Floating IP or private IP address from an instance in your private network. - -/// +### Creating the Load Balancer + +> [!tabs] +> Via the OVHcloud Control Panel +>> Log in to the [OVHcloud Control Panel](/links/manager), go to the `Public Cloud`{.action} section and select the Public Cloud project concerned. 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: Region choice** +>> +>> ![Region choice](images/region.png){.thumbnail} +>> +>> 1. **Select the zone type:** +>> +>> - 1AZ: Deployment in a single availability zone. +>> - 3AZ: Deployment spread across three availability zones for high availability. +>> +>> 2. **Choose the region:** Only regions where you have a private network and at least one subnet can be selected. Select the region and click `Next`{.action}. +>> +>> **Step 2: 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 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`{.action}. +>> +>> **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](/pages/public_cloud/public_cloud_network_services/concepts-03-loadbalancer#operating-provisioning-status)" page. +>> +> Via the OpenStack CLI +>> Another way to create a Load Balancer is through the OpenStack Command Line Interface. Before you begin, consult the following guides: +>> +>> - [Preparing an environment for using the OpenStack API](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api). +>> - [Setting OpenStack environment variables](/pages/public_cloud/public_cloud_cross_functional/loading_openstack_environment_variables). +>> +>> **Configuring your private network** +>> +>> Before creating a Load Balancer, you will need to set up a private network: +>> +>> ```bash +>> openstack network create my_network +>> +>> openstack subnet create my_subnet --subnet-range --network my_network --no-dhcp +>> +>> openstack router create my_router +>> +>> openstack router add subnet my_router my_subnet +>> +>> openstack router set --external-gateway Ext-Net my_router +>> ``` +>> +>> You can now attach your instances to the new network. We recommend following our guide to [integrate an instance into vRack](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#instance-integration). +>> +>> List the addresses of your instances in your network with the following command: +>> +>> ```bash +>> openstack server list +>> ``` +>> +>> In the next step, configure the network interfaces of your instances according to this output. +>> +>> **Creating the Load Balancer** +>> +>> You can view a list of the different Load Balancer flavors we offer with this command: +>> +>> ```bash +>> openstack loadbalancer flavor list +>> ``` +>> +>> You can now create your Load Balancer with the following command. In this example, we will create a "Small" Load Balancer. +>> +>> ```bash +>> openstack loadbalancer create --name my_load_balancer --flavor small --vip-subnet-id my_subnet +>> ``` +>> +>> Your Load Balancer will be configured with an IP address of the private network. If you want to have access from the internet, you will need to attach a Floating IP address. +>> +>> **Attaching a Floating IP address to a Load Balancer** +>> +>> This is how to attach a Floating IP address to a Load Balancer: +>> +>> ```bash +>> openstack floating ip create Ext-Net +>> openstack floating ip set --port +>> ``` +>> +>> > [!primary] +>> > +>> > To retrieve the VIP port ID of your Load Balancer, use `openstack loadbalancer show my_load_balancer`. +>> > +>> +>> **Configuring your Load Balancer** +>> +>> In this example we will configure an HTTP Load Balancer. In order to listen on port 80 of the Load Balancer, create a Listener with this command: +>> +>> ```bash +>> openstack loadbalancer listener create --name my_listener_http --protocol HTTP --protocol-port 80 my_loadbalancer +>> ``` +>> +>> Once the Listener has been created, you need to add each instance that can respond to external requests. To do this, you must create an Instance Pool: +>> +>> ```bash +>> openstack loadbalancer pool create --name my_pool_http --lb-algorithm ROUND_ROBIN --listener my_listener --protocol HTTP +>> ``` +>> +>> Add your instances to the Instance Pool: +>> +>> ```bash +>> openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool +>> openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool +>> ``` +>> +>> You can now access your Load Balancer via the Floating IP or private IP address from an instance in your private network. +>> ## Go further diff --git a/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.en-sg.md b/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.en-sg.md index eb8a711e9f4..1fa20d549eb 100644 --- a/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.en-sg.md +++ b/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.en-sg.md @@ -1,23 +1,9 @@ --- title: Getting started with Load Balancer on Public Cloud excerpt: Discover how to launch a Load Balancer on Public Cloud -updated: 2025-04-28 +updated: 2025-11-03 --- - - ## Objective Our Public Cloud Load Balancer is based on [OpenStack Octavia](https://wiki.openstack.org/wiki/Octavia) and is fully integrated into the Public Cloud universe. @@ -34,152 +20,156 @@ Our Public Cloud Load Balancer is based on [OpenStack Octavia](https://wiki.ope ## Instructions -### Creating the Load Balancer from the OVHcloud Control Panel - -Log in to the [OVHcloud Control Panel](/links/manager), go to the `Public Cloud`{.action} section and select the Public Cloud project concerned. 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). - -### Creating the Load Balancer from the Openstack Command Line Interface - -/// details | Unfold this section - -Another way to create a Load Balancer is through the Openstack Command Line Interface. Before you begin, consult the following guides: - -[Preparing an environment for using the OpenStack API](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api).
-[Setting OpenStack environment variables](/pages/public_cloud/public_cloud_cross_functional/loading_openstack_environment_variables). - -#### Configuring your private network - -Before creating a Load Balancer, you will need to set up a private network: - -```bash -openstack network create my_network - -openstack subnet create my_subnet --subnet-range --network my_network --no-dhcp - -openstack router create my_router - -openstack router add subnet my_router my_subnet - -openstack router set --external-gateway Ext-Net my_router -``` - -You can now attach your instances to the new network. We recommend following our guide to [integrate an instance into vRack](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#instance-integration). List the addresses of your instances in your network with the following command: - -```bash -openstack server list -``` - -In the next step, configure the network interfaces of your instances according to this output. - -#### Creating the Load Balancer - -You can view a list of the different Load Balancer flavors we offer with this command: - -```bash -openstack loadbalancer flavor list -``` - -You can now create your Load Balancer with the following command. In this example, we will create a "Small" Load Balancer. - -```bash -openstack loadbalancer create --name my_load_balancer --flavor small --vip-subnet-id my_subnet -``` - -Your Load Balancer will be configured with an IP address of the private network. If you want to have access from the internet, you will need to attach a Floating IP address. - -#### Attaching a Floating IP address to a Load Balancer - -This is how to attach a Floating IP address to a Load Balancer: - -```bash -openstack floating ip create Ext-Net -openstack floating ip set --port -``` - -> [!primary] -> -> To retrieve the VIP port ID of your Load Balancer, use `openstack loadbalancer show my_load_balancer`. - -#### Configuring your Load Balancer - -In this example we will configure an HTTP Load Balancer. In order to listen on port 80 of the Load Balancer, create a Listener with this command: - -```bash -openstack loadbalancer listener create --name my_listener_http --protocol HTTP --protocol-port 80 my_loadbalancer -``` - -Once the Listener has been created, you need to add each instance that can respond to external requests. To do this, you must create an Instance Pool: - -```bash -openstack loadbalancer pool create --name my_pool_http --lb-algorithm ROUND_ROBIN --listener my_listener --protocol HTTP -``` - -Add your instances to the Instance Pool: - -```bash -openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool -openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool -``` - -You can now access your Load Balancer via the Floating IP or private IP address from an instance in your private network. - -/// +### Creating the Load Balancer + +> [!tabs] +> Via the OVHcloud Control Panel +>> Log in to the [OVHcloud Control Panel](/links/manager), go to the `Public Cloud`{.action} section and select the Public Cloud project concerned. 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: Region choice** +>> +>> ![Region choice](images/region.png){.thumbnail} +>> +>> 1. **Select the zone type:** +>> +>> - 1AZ: Deployment in a single availability zone. +>> - 3AZ: Deployment spread across three availability zones for high availability. +>> +>> 2. **Choose the region:** Only regions where you have a private network and at least one subnet can be selected. Select the region and click `Next`{.action}. +>> +>> **Step 2: 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 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`{.action}. +>> +>> **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](/pages/public_cloud/public_cloud_network_services/concepts-03-loadbalancer#operating-provisioning-status)" page. +>> +> Via the OpenStack CLI +>> Another way to create a Load Balancer is through the OpenStack Command Line Interface. Before you begin, consult the following guides: +>> +>> - [Preparing an environment for using the OpenStack API](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api). +>> - [Setting OpenStack environment variables](/pages/public_cloud/public_cloud_cross_functional/loading_openstack_environment_variables). +>> +>> **Configuring your private network** +>> +>> Before creating a Load Balancer, you will need to set up a private network: +>> +>> ```bash +>> openstack network create my_network +>> +>> openstack subnet create my_subnet --subnet-range --network my_network --no-dhcp +>> +>> openstack router create my_router +>> +>> openstack router add subnet my_router my_subnet +>> +>> openstack router set --external-gateway Ext-Net my_router +>> ``` +>> +>> You can now attach your instances to the new network. We recommend following our guide to [integrate an instance into vRack](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#instance-integration). +>> +>> List the addresses of your instances in your network with the following command: +>> +>> ```bash +>> openstack server list +>> ``` +>> +>> In the next step, configure the network interfaces of your instances according to this output. +>> +>> **Creating the Load Balancer** +>> +>> You can view a list of the different Load Balancer flavors we offer with this command: +>> +>> ```bash +>> openstack loadbalancer flavor list +>> ``` +>> +>> You can now create your Load Balancer with the following command. In this example, we will create a "Small" Load Balancer. +>> +>> ```bash +>> openstack loadbalancer create --name my_load_balancer --flavor small --vip-subnet-id my_subnet +>> ``` +>> +>> Your Load Balancer will be configured with an IP address of the private network. If you want to have access from the internet, you will need to attach a Floating IP address. +>> +>> **Attaching a Floating IP address to a Load Balancer** +>> +>> This is how to attach a Floating IP address to a Load Balancer: +>> +>> ```bash +>> openstack floating ip create Ext-Net +>> openstack floating ip set --port +>> ``` +>> +>> > [!primary] +>> > +>> > To retrieve the VIP port ID of your Load Balancer, use `openstack loadbalancer show my_load_balancer`. +>> > +>> +>> **Configuring your Load Balancer** +>> +>> In this example we will configure an HTTP Load Balancer. In order to listen on port 80 of the Load Balancer, create a Listener with this command: +>> +>> ```bash +>> openstack loadbalancer listener create --name my_listener_http --protocol HTTP --protocol-port 80 my_loadbalancer +>> ``` +>> +>> Once the Listener has been created, you need to add each instance that can respond to external requests. To do this, you must create an Instance Pool: +>> +>> ```bash +>> openstack loadbalancer pool create --name my_pool_http --lb-algorithm ROUND_ROBIN --listener my_listener --protocol HTTP +>> ``` +>> +>> Add your instances to the Instance Pool: +>> +>> ```bash +>> openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool +>> openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool +>> ``` +>> +>> You can now access your Load Balancer via the Floating IP or private IP address from an instance in your private network. +>> ## Go further diff --git a/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.en-us.md b/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.en-us.md index eb8a711e9f4..1fa20d549eb 100644 --- a/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.en-us.md +++ b/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.en-us.md @@ -1,23 +1,9 @@ --- title: Getting started with Load Balancer on Public Cloud excerpt: Discover how to launch a Load Balancer on Public Cloud -updated: 2025-04-28 +updated: 2025-11-03 --- - - ## Objective Our Public Cloud Load Balancer is based on [OpenStack Octavia](https://wiki.openstack.org/wiki/Octavia) and is fully integrated into the Public Cloud universe. @@ -34,152 +20,156 @@ Our Public Cloud Load Balancer is based on [OpenStack Octavia](https://wiki.ope ## Instructions -### Creating the Load Balancer from the OVHcloud Control Panel - -Log in to the [OVHcloud Control Panel](/links/manager), go to the `Public Cloud`{.action} section and select the Public Cloud project concerned. 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). - -### Creating the Load Balancer from the Openstack Command Line Interface - -/// details | Unfold this section - -Another way to create a Load Balancer is through the Openstack Command Line Interface. Before you begin, consult the following guides: - -[Preparing an environment for using the OpenStack API](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api).
-[Setting OpenStack environment variables](/pages/public_cloud/public_cloud_cross_functional/loading_openstack_environment_variables). - -#### Configuring your private network - -Before creating a Load Balancer, you will need to set up a private network: - -```bash -openstack network create my_network - -openstack subnet create my_subnet --subnet-range --network my_network --no-dhcp - -openstack router create my_router - -openstack router add subnet my_router my_subnet - -openstack router set --external-gateway Ext-Net my_router -``` - -You can now attach your instances to the new network. We recommend following our guide to [integrate an instance into vRack](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#instance-integration). List the addresses of your instances in your network with the following command: - -```bash -openstack server list -``` - -In the next step, configure the network interfaces of your instances according to this output. - -#### Creating the Load Balancer - -You can view a list of the different Load Balancer flavors we offer with this command: - -```bash -openstack loadbalancer flavor list -``` - -You can now create your Load Balancer with the following command. In this example, we will create a "Small" Load Balancer. - -```bash -openstack loadbalancer create --name my_load_balancer --flavor small --vip-subnet-id my_subnet -``` - -Your Load Balancer will be configured with an IP address of the private network. If you want to have access from the internet, you will need to attach a Floating IP address. - -#### Attaching a Floating IP address to a Load Balancer - -This is how to attach a Floating IP address to a Load Balancer: - -```bash -openstack floating ip create Ext-Net -openstack floating ip set --port -``` - -> [!primary] -> -> To retrieve the VIP port ID of your Load Balancer, use `openstack loadbalancer show my_load_balancer`. - -#### Configuring your Load Balancer - -In this example we will configure an HTTP Load Balancer. In order to listen on port 80 of the Load Balancer, create a Listener with this command: - -```bash -openstack loadbalancer listener create --name my_listener_http --protocol HTTP --protocol-port 80 my_loadbalancer -``` - -Once the Listener has been created, you need to add each instance that can respond to external requests. To do this, you must create an Instance Pool: - -```bash -openstack loadbalancer pool create --name my_pool_http --lb-algorithm ROUND_ROBIN --listener my_listener --protocol HTTP -``` - -Add your instances to the Instance Pool: - -```bash -openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool -openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool -``` - -You can now access your Load Balancer via the Floating IP or private IP address from an instance in your private network. - -/// +### Creating the Load Balancer + +> [!tabs] +> Via the OVHcloud Control Panel +>> Log in to the [OVHcloud Control Panel](/links/manager), go to the `Public Cloud`{.action} section and select the Public Cloud project concerned. 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: Region choice** +>> +>> ![Region choice](images/region.png){.thumbnail} +>> +>> 1. **Select the zone type:** +>> +>> - 1AZ: Deployment in a single availability zone. +>> - 3AZ: Deployment spread across three availability zones for high availability. +>> +>> 2. **Choose the region:** Only regions where you have a private network and at least one subnet can be selected. Select the region and click `Next`{.action}. +>> +>> **Step 2: 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 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`{.action}. +>> +>> **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](/pages/public_cloud/public_cloud_network_services/concepts-03-loadbalancer#operating-provisioning-status)" page. +>> +> Via the OpenStack CLI +>> Another way to create a Load Balancer is through the OpenStack Command Line Interface. Before you begin, consult the following guides: +>> +>> - [Preparing an environment for using the OpenStack API](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api). +>> - [Setting OpenStack environment variables](/pages/public_cloud/public_cloud_cross_functional/loading_openstack_environment_variables). +>> +>> **Configuring your private network** +>> +>> Before creating a Load Balancer, you will need to set up a private network: +>> +>> ```bash +>> openstack network create my_network +>> +>> openstack subnet create my_subnet --subnet-range --network my_network --no-dhcp +>> +>> openstack router create my_router +>> +>> openstack router add subnet my_router my_subnet +>> +>> openstack router set --external-gateway Ext-Net my_router +>> ``` +>> +>> You can now attach your instances to the new network. We recommend following our guide to [integrate an instance into vRack](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#instance-integration). +>> +>> List the addresses of your instances in your network with the following command: +>> +>> ```bash +>> openstack server list +>> ``` +>> +>> In the next step, configure the network interfaces of your instances according to this output. +>> +>> **Creating the Load Balancer** +>> +>> You can view a list of the different Load Balancer flavors we offer with this command: +>> +>> ```bash +>> openstack loadbalancer flavor list +>> ``` +>> +>> You can now create your Load Balancer with the following command. In this example, we will create a "Small" Load Balancer. +>> +>> ```bash +>> openstack loadbalancer create --name my_load_balancer --flavor small --vip-subnet-id my_subnet +>> ``` +>> +>> Your Load Balancer will be configured with an IP address of the private network. If you want to have access from the internet, you will need to attach a Floating IP address. +>> +>> **Attaching a Floating IP address to a Load Balancer** +>> +>> This is how to attach a Floating IP address to a Load Balancer: +>> +>> ```bash +>> openstack floating ip create Ext-Net +>> openstack floating ip set --port +>> ``` +>> +>> > [!primary] +>> > +>> > To retrieve the VIP port ID of your Load Balancer, use `openstack loadbalancer show my_load_balancer`. +>> > +>> +>> **Configuring your Load Balancer** +>> +>> In this example we will configure an HTTP Load Balancer. In order to listen on port 80 of the Load Balancer, create a Listener with this command: +>> +>> ```bash +>> openstack loadbalancer listener create --name my_listener_http --protocol HTTP --protocol-port 80 my_loadbalancer +>> ``` +>> +>> Once the Listener has been created, you need to add each instance that can respond to external requests. To do this, you must create an Instance Pool: +>> +>> ```bash +>> openstack loadbalancer pool create --name my_pool_http --lb-algorithm ROUND_ROBIN --listener my_listener --protocol HTTP +>> ``` +>> +>> Add your instances to the Instance Pool: +>> +>> ```bash +>> openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool +>> openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool +>> ``` +>> +>> You can now access your Load Balancer via the Floating IP or private IP address from an instance in your private network. +>> ## Go further diff --git a/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.es-es.md b/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.es-es.md index 7baf1c4aac6..1fa20d549eb 100644 --- a/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.es-es.md +++ b/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.es-es.md @@ -1,23 +1,9 @@ --- -title: Getting started with Load Balancer on Public Cloud (EN) +title: Getting started with Load Balancer on Public Cloud excerpt: Discover how to launch a Load Balancer on Public Cloud -updated: 2025-04-28 +updated: 2025-11-03 --- - - ## Objective Our Public Cloud Load Balancer is based on [OpenStack Octavia](https://wiki.openstack.org/wiki/Octavia) and is fully integrated into the Public Cloud universe. @@ -34,152 +20,156 @@ Our Public Cloud Load Balancer is based on [OpenStack Octavia](https://wiki.ope ## Instructions -### Creating the Load Balancer from the OVHcloud Control Panel - -Log in to the [OVHcloud Control Panel](/links/manager), go to the `Public Cloud`{.action} section and select the Public Cloud project concerned. 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). - -### Creating the Load Balancer from the Openstack Command Line Interface - -/// details | Unfold this section - -Another way to create a Load Balancer is through the Openstack Command Line Interface. Before you begin, consult the following guides: - -[Preparing an environment for using the OpenStack API](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api).
-[Setting OpenStack environment variables](/pages/public_cloud/public_cloud_cross_functional/loading_openstack_environment_variables). - -#### Configuring your private network - -Before creating a Load Balancer, you will need to set up a private network: - -```bash -openstack network create my_network - -openstack subnet create my_subnet --subnet-range --network my_network --no-dhcp - -openstack router create my_router - -openstack router add subnet my_router my_subnet - -openstack router set --external-gateway Ext-Net my_router -``` - -You can now attach your instances to the new network. We recommend following our guide to [integrate an instance into vRack](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#instance-integration). List the addresses of your instances in your network with the following command: - -```bash -openstack server list -``` - -In the next step, configure the network interfaces of your instances according to this output. - -#### Creating the Load Balancer - -You can view a list of the different Load Balancer flavors we offer with this command: - -```bash -openstack loadbalancer flavor list -``` - -You can now create your Load Balancer with the following command. In this example, we will create a "Small" Load Balancer. - -```bash -openstack loadbalancer create --name my_load_balancer --flavor small --vip-subnet-id my_subnet -``` - -Your Load Balancer will be configured with an IP address of the private network. If you want to have access from the internet, you will need to attach a Floating IP address. - -#### Attaching a Floating IP address to a Load Balancer - -This is how to attach a Floating IP address to a Load Balancer: - -```bash -openstack floating ip create Ext-Net -openstack floating ip set --port -``` - -> [!primary] -> -> To retrieve the VIP port ID of your Load Balancer, use `openstack loadbalancer show my_load_balancer`. - -#### Configuring your Load Balancer - -In this example we will configure an HTTP Load Balancer. In order to listen on port 80 of the Load Balancer, create a Listener with this command: - -```bash -openstack loadbalancer listener create --name my_listener_http --protocol HTTP --protocol-port 80 my_loadbalancer -``` - -Once the Listener has been created, you need to add each instance that can respond to external requests. To do this, you must create an Instance Pool: - -```bash -openstack loadbalancer pool create --name my_pool_http --lb-algorithm ROUND_ROBIN --listener my_listener --protocol HTTP -``` - -Add your instances to the Instance Pool: - -```bash -openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool -openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool -``` - -You can now access your Load Balancer via the Floating IP or private IP address from an instance in your private network. - -/// +### Creating the Load Balancer + +> [!tabs] +> Via the OVHcloud Control Panel +>> Log in to the [OVHcloud Control Panel](/links/manager), go to the `Public Cloud`{.action} section and select the Public Cloud project concerned. 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: Region choice** +>> +>> ![Region choice](images/region.png){.thumbnail} +>> +>> 1. **Select the zone type:** +>> +>> - 1AZ: Deployment in a single availability zone. +>> - 3AZ: Deployment spread across three availability zones for high availability. +>> +>> 2. **Choose the region:** Only regions where you have a private network and at least one subnet can be selected. Select the region and click `Next`{.action}. +>> +>> **Step 2: 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 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`{.action}. +>> +>> **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](/pages/public_cloud/public_cloud_network_services/concepts-03-loadbalancer#operating-provisioning-status)" page. +>> +> Via the OpenStack CLI +>> Another way to create a Load Balancer is through the OpenStack Command Line Interface. Before you begin, consult the following guides: +>> +>> - [Preparing an environment for using the OpenStack API](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api). +>> - [Setting OpenStack environment variables](/pages/public_cloud/public_cloud_cross_functional/loading_openstack_environment_variables). +>> +>> **Configuring your private network** +>> +>> Before creating a Load Balancer, you will need to set up a private network: +>> +>> ```bash +>> openstack network create my_network +>> +>> openstack subnet create my_subnet --subnet-range --network my_network --no-dhcp +>> +>> openstack router create my_router +>> +>> openstack router add subnet my_router my_subnet +>> +>> openstack router set --external-gateway Ext-Net my_router +>> ``` +>> +>> You can now attach your instances to the new network. We recommend following our guide to [integrate an instance into vRack](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#instance-integration). +>> +>> List the addresses of your instances in your network with the following command: +>> +>> ```bash +>> openstack server list +>> ``` +>> +>> In the next step, configure the network interfaces of your instances according to this output. +>> +>> **Creating the Load Balancer** +>> +>> You can view a list of the different Load Balancer flavors we offer with this command: +>> +>> ```bash +>> openstack loadbalancer flavor list +>> ``` +>> +>> You can now create your Load Balancer with the following command. In this example, we will create a "Small" Load Balancer. +>> +>> ```bash +>> openstack loadbalancer create --name my_load_balancer --flavor small --vip-subnet-id my_subnet +>> ``` +>> +>> Your Load Balancer will be configured with an IP address of the private network. If you want to have access from the internet, you will need to attach a Floating IP address. +>> +>> **Attaching a Floating IP address to a Load Balancer** +>> +>> This is how to attach a Floating IP address to a Load Balancer: +>> +>> ```bash +>> openstack floating ip create Ext-Net +>> openstack floating ip set --port +>> ``` +>> +>> > [!primary] +>> > +>> > To retrieve the VIP port ID of your Load Balancer, use `openstack loadbalancer show my_load_balancer`. +>> > +>> +>> **Configuring your Load Balancer** +>> +>> In this example we will configure an HTTP Load Balancer. In order to listen on port 80 of the Load Balancer, create a Listener with this command: +>> +>> ```bash +>> openstack loadbalancer listener create --name my_listener_http --protocol HTTP --protocol-port 80 my_loadbalancer +>> ``` +>> +>> Once the Listener has been created, you need to add each instance that can respond to external requests. To do this, you must create an Instance Pool: +>> +>> ```bash +>> openstack loadbalancer pool create --name my_pool_http --lb-algorithm ROUND_ROBIN --listener my_listener --protocol HTTP +>> ``` +>> +>> Add your instances to the Instance Pool: +>> +>> ```bash +>> openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool +>> openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool +>> ``` +>> +>> You can now access your Load Balancer via the Floating IP or private IP address from an instance in your private network. +>> ## Go further diff --git a/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.es-us.md b/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.es-us.md index 7baf1c4aac6..1fa20d549eb 100644 --- a/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.es-us.md +++ b/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.es-us.md @@ -1,23 +1,9 @@ --- -title: Getting started with Load Balancer on Public Cloud (EN) +title: Getting started with Load Balancer on Public Cloud excerpt: Discover how to launch a Load Balancer on Public Cloud -updated: 2025-04-28 +updated: 2025-11-03 --- - - ## Objective Our Public Cloud Load Balancer is based on [OpenStack Octavia](https://wiki.openstack.org/wiki/Octavia) and is fully integrated into the Public Cloud universe. @@ -34,152 +20,156 @@ Our Public Cloud Load Balancer is based on [OpenStack Octavia](https://wiki.ope ## Instructions -### Creating the Load Balancer from the OVHcloud Control Panel - -Log in to the [OVHcloud Control Panel](/links/manager), go to the `Public Cloud`{.action} section and select the Public Cloud project concerned. 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). - -### Creating the Load Balancer from the Openstack Command Line Interface - -/// details | Unfold this section - -Another way to create a Load Balancer is through the Openstack Command Line Interface. Before you begin, consult the following guides: - -[Preparing an environment for using the OpenStack API](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api).
-[Setting OpenStack environment variables](/pages/public_cloud/public_cloud_cross_functional/loading_openstack_environment_variables). - -#### Configuring your private network - -Before creating a Load Balancer, you will need to set up a private network: - -```bash -openstack network create my_network - -openstack subnet create my_subnet --subnet-range --network my_network --no-dhcp - -openstack router create my_router - -openstack router add subnet my_router my_subnet - -openstack router set --external-gateway Ext-Net my_router -``` - -You can now attach your instances to the new network. We recommend following our guide to [integrate an instance into vRack](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#instance-integration). List the addresses of your instances in your network with the following command: - -```bash -openstack server list -``` - -In the next step, configure the network interfaces of your instances according to this output. - -#### Creating the Load Balancer - -You can view a list of the different Load Balancer flavors we offer with this command: - -```bash -openstack loadbalancer flavor list -``` - -You can now create your Load Balancer with the following command. In this example, we will create a "Small" Load Balancer. - -```bash -openstack loadbalancer create --name my_load_balancer --flavor small --vip-subnet-id my_subnet -``` - -Your Load Balancer will be configured with an IP address of the private network. If you want to have access from the internet, you will need to attach a Floating IP address. - -#### Attaching a Floating IP address to a Load Balancer - -This is how to attach a Floating IP address to a Load Balancer: - -```bash -openstack floating ip create Ext-Net -openstack floating ip set --port -``` - -> [!primary] -> -> To retrieve the VIP port ID of your Load Balancer, use `openstack loadbalancer show my_load_balancer`. - -#### Configuring your Load Balancer - -In this example we will configure an HTTP Load Balancer. In order to listen on port 80 of the Load Balancer, create a Listener with this command: - -```bash -openstack loadbalancer listener create --name my_listener_http --protocol HTTP --protocol-port 80 my_loadbalancer -``` - -Once the Listener has been created, you need to add each instance that can respond to external requests. To do this, you must create an Instance Pool: - -```bash -openstack loadbalancer pool create --name my_pool_http --lb-algorithm ROUND_ROBIN --listener my_listener --protocol HTTP -``` - -Add your instances to the Instance Pool: - -```bash -openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool -openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool -``` - -You can now access your Load Balancer via the Floating IP or private IP address from an instance in your private network. - -/// +### Creating the Load Balancer + +> [!tabs] +> Via the OVHcloud Control Panel +>> Log in to the [OVHcloud Control Panel](/links/manager), go to the `Public Cloud`{.action} section and select the Public Cloud project concerned. 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: Region choice** +>> +>> ![Region choice](images/region.png){.thumbnail} +>> +>> 1. **Select the zone type:** +>> +>> - 1AZ: Deployment in a single availability zone. +>> - 3AZ: Deployment spread across three availability zones for high availability. +>> +>> 2. **Choose the region:** Only regions where you have a private network and at least one subnet can be selected. Select the region and click `Next`{.action}. +>> +>> **Step 2: 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 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`{.action}. +>> +>> **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](/pages/public_cloud/public_cloud_network_services/concepts-03-loadbalancer#operating-provisioning-status)" page. +>> +> Via the OpenStack CLI +>> Another way to create a Load Balancer is through the OpenStack Command Line Interface. Before you begin, consult the following guides: +>> +>> - [Preparing an environment for using the OpenStack API](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api). +>> - [Setting OpenStack environment variables](/pages/public_cloud/public_cloud_cross_functional/loading_openstack_environment_variables). +>> +>> **Configuring your private network** +>> +>> Before creating a Load Balancer, you will need to set up a private network: +>> +>> ```bash +>> openstack network create my_network +>> +>> openstack subnet create my_subnet --subnet-range --network my_network --no-dhcp +>> +>> openstack router create my_router +>> +>> openstack router add subnet my_router my_subnet +>> +>> openstack router set --external-gateway Ext-Net my_router +>> ``` +>> +>> You can now attach your instances to the new network. We recommend following our guide to [integrate an instance into vRack](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#instance-integration). +>> +>> List the addresses of your instances in your network with the following command: +>> +>> ```bash +>> openstack server list +>> ``` +>> +>> In the next step, configure the network interfaces of your instances according to this output. +>> +>> **Creating the Load Balancer** +>> +>> You can view a list of the different Load Balancer flavors we offer with this command: +>> +>> ```bash +>> openstack loadbalancer flavor list +>> ``` +>> +>> You can now create your Load Balancer with the following command. In this example, we will create a "Small" Load Balancer. +>> +>> ```bash +>> openstack loadbalancer create --name my_load_balancer --flavor small --vip-subnet-id my_subnet +>> ``` +>> +>> Your Load Balancer will be configured with an IP address of the private network. If you want to have access from the internet, you will need to attach a Floating IP address. +>> +>> **Attaching a Floating IP address to a Load Balancer** +>> +>> This is how to attach a Floating IP address to a Load Balancer: +>> +>> ```bash +>> openstack floating ip create Ext-Net +>> openstack floating ip set --port +>> ``` +>> +>> > [!primary] +>> > +>> > To retrieve the VIP port ID of your Load Balancer, use `openstack loadbalancer show my_load_balancer`. +>> > +>> +>> **Configuring your Load Balancer** +>> +>> In this example we will configure an HTTP Load Balancer. In order to listen on port 80 of the Load Balancer, create a Listener with this command: +>> +>> ```bash +>> openstack loadbalancer listener create --name my_listener_http --protocol HTTP --protocol-port 80 my_loadbalancer +>> ``` +>> +>> Once the Listener has been created, you need to add each instance that can respond to external requests. To do this, you must create an Instance Pool: +>> +>> ```bash +>> openstack loadbalancer pool create --name my_pool_http --lb-algorithm ROUND_ROBIN --listener my_listener --protocol HTTP +>> ``` +>> +>> Add your instances to the Instance Pool: +>> +>> ```bash +>> openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool +>> openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool +>> ``` +>> +>> You can now access your Load Balancer via the Floating IP or private IP address from an instance in your private network. +>> ## Go further diff --git a/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.fr-ca.md b/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.fr-ca.md index 762a91597e0..e33ec9f32ff 100644 --- a/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.fr-ca.md +++ b/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.fr-ca.md @@ -1,23 +1,9 @@ --- title: Premiers pas avec le service Load Balancer pour Public Cloud excerpt: Découvrez comment débuter avec un Load Balancer Public Cloud -updated: 2025-04-28 +updated: 2025-11-03 --- - - ## Objectif Notre Load Balancer Public Cloud est basé sur le service [Openstack Octavia](https://wiki.openstack.org/wiki/Octavia) et est entièrement intégré dans l'univers Public Cloud. @@ -32,55 +18,53 @@ Notre Load Balancer Public Cloud est basé sur le service [Openstack Octavia](ht - Un Load Balancer nécessite un sous-réseau, lisez [ce guide](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack) pour plus d'informations - (Facultatif) : Ce guide explique la configuration du load balancer via l'interface graphique et l'interface en ligne de commande. Si vous souhaitez utiliser cette dernière, installez [l'environnement en ligne de commande OpenStack](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api) - ## En pratique -### Création du Load Balancer depuis votre espace client OVHcloud - -/// details | Dépliez cette section - -> [!success] -> Cliquez sur les onglets ci-dessous pour visualiser chacune des 6 étapes. +### Création du Load Balancer > [!tabs] ->> +> Via l'espace client OVHcloud >> Connectez-vous à l’[espace client OVHcloud](/links/manager), rendez-vous dans la section `Public Cloud`{.action} et sélectionnez le projet Public Cloud concerné. Cliquez sur `Load Balancer`{.action} (sous **Network**) dans le menu de gauche, puis cliquez sur le bouton `Créer un Load Balancer`{.action}. >> >> La page de configuration s'ouvre. >> -> **Étape 1 : Choix de la taille** +>> **Étape 1 : Choix de la région** >> ->> ![Choix de la taille](images/size.png){.thumbnail} +>> ![Choix de la région](images/region.png){.thumbnail} >> ->> L'interface contient un lien vers notre site sur lequel les caractéristiques / benchmark de toutes tailles sont fournies. Une fois que vous avez choisi votre taille, cliquez sur `Suivant`{.action}. +>> 1. **Sélectionnez le type de zone :** >> +>> - 1AZ : Déploiement sur une seule zone de disponibilité. +>> - 3AZ : Déploiement réparti sur trois zones pour une haute disponibilité. >> -> **Étape 2 : Choix de la région** +>> 2. **Choisissez la région :** Seules les régions sur lesquelles vous avez un réseau privé et au moins un sous-réseau peuvent être sélectionnées. Sélectionnez la région et cliquez sur `Suivant`{.action}. >> ->> ![Choix de la région](images/region.png){.thumbnail} +>> **Étape 2 : Choix de la taille** +>> +>> ![Choix de la taille](images/size.png){.thumbnail} >> ->> Seules les régions sur lesquelles vous avez un réseau privé et au moins un sous-réseau peuvent être sélectionnées. Sélectionnez la région et cliquez sur `Suivant`{.action}. +>> L'interface contient un lien vers notre site sur lequel les caractéristiques et un benchmark de toutes les tailles sont fournis. Une fois que vous avez choisi votre taille, cliquez sur `Suivant`{.action}. >> -> **Étape 3 : attacher une IP publique (ou non)** +>> **Étape 3 : Attacher une IP publique (ou non)** >> >> ![Public IP choice](images/floating_IP.png){.thumbnail} >> ->> À ce stade, vous devez savoir si votre Load Balancer recevra du trafic public ou non (pour plus de détails, consultez notre page « [Concepts - Réseau Public Cloud](/pages/public_cloud/public_cloud_network_services/concepts-01-public-cloud-networking-concepts)) ». +>> À ce stade, vous devez savoir si votre Load Balancer recevra du trafic public ou non (pour plus de détails, consultez notre page « [Concepts - Réseau Public Cloud](/pages/public_cloud/public_cloud_network_services/concepts-01-public-cloud-networking-concepts)) ». >> >> Si votre Load Balancer reçoit du trafic public, vous disposez de 2 options : >> ->> - `Nouvelle IP Publique` : cette option créera une nouvelle adresse Floating IP pour votre Load Balancer. +>> - `Nouvelle IP Publique` : Cette option créera une nouvelle adresse Floating IP pour votre Load Balancer. >> - Si vous avez déjà une adresse Floating IP, l'interface vous proposera d'en choisir une. >> ->> Si votre Load Balancer ne doit recevoir que du trafic privé, choisissez « Aucune IP publique ». +>> Si votre Load Balancer ne doit recevoir que du trafic privé, choisissez `Aucune IP publique`{.action}. >> -> **Étape 4 : sélectionnez le réseau privé et le sous-réseau sur lesquels le Load Balancer sera créé** +>> **Étape 4 : Sélectionner le réseau privé et le sous-réseau sur lesquels le Load Balancer sera créé** >> >> ![Choix du réseau](images/private_network.png){.thumbnail} >> >> L'interface vous informera si le réseau privé ou le sous-réseau ne sont pas conformes aux prérequis (voir notre page « [Concepts - Load Balancer](/pages/public_cloud/public_cloud_network_services/concepts-03-loadbalancer#network-prerequisites) »). >> -> **Étape 5 (facultatif) : définir le ou les listeners et les membres** +>> **Étape 5 (facultatif) : Définir le ou les listeners et les membres** >> >> ![Choix du listener](images/listener.png){.thumbnail} >> @@ -89,108 +73,101 @@ Notre Load Balancer Public Cloud est basé sur le service [Openstack Octavia](ht >> - Enfin, parmi les instances de votre région, choisissez l'IP et le port membre qui feront partie du pool. Notez que pour simplifier le processus de configuration, votre pool doit avoir le même protocole que le listener, et que le membre ne peut être choisi qu'à partir de l'instance. Ces limitations peuvent être contournées en ignorant cette partie de la configuration et en utilisant la configuration du pool/membre une fois le Load Balancer créé. >> >> > [!primary] ->> > >> > Pour simplifier le processus de configuration, votre pool doit avoir le même protocole que le listener et le membre ne peut être choisi qu'à partir d'une instance. De plus, l'algorithme de load balancing par défaut est : `ROUND_ROBIN`. >> > Ces limitations peuvent être contournées en ignorant cette partie de la configuration et en utilisant la configuration du pool/membre une fois le Load Balancer créé. >> > >> -> **Étape 6 : Définir le nom du Load Balancer** +>> **Étape 6 : Définir le nom du Load Balancer** >> >> ![Name](images/name.png){.thumbnail} >> >> Vous pouvez définir un nom pour le Load Balancer et cliquer sur `Créer un Load Balancer`{.action}. >> ->> Vous allez être redirigé vers la page qui liste les Load Balancers. Parmi les attributs qui s'affichent, les `Operating status` et `Provisioning status` fournissent des informations sur l'état de votre load balancer. Retrouvez plus d'informations sur la [page Concepts du Load Balancer](/pages/public_cloud/public_cloud_network_services/concepts-03-loadbalancer#operating-provisioning-status). ->> - -/// - -### Création du Load Balancer via l'interface en ligne de commande (CLI) Openstack - -/// details | Dépliez cette section - -Une autre façon de créer un Load Balance est d'utiliser l'interface de ligne de commande d'Openstack. Avant de commencer, consultez les guides suivants : - -[Preparing an environment for using the OpenStack API](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api).
-[Setting OpenStack environment variables](/pages/public_cloud/public_cloud_cross_functional/loading_openstack_environment_variables). - -#### Configurer votre réseau privé - -Avant de commencer à utiliser un Load Balancer, il vous faut créer un réseau privé : - -```bash -openstack network create my_network - -openstack subnet create my_subnet --subnet-range --network my_network --no-dhcp - -openstack router create my_router - -openstack router add subnet my_router my_subnet - -openstack router set --external-gateway Ext-Net my_router -``` - -Vous pouvez maintenant attacher vos instances à ce nouveau réseau. Nous vous recommandons de suivre la documentation pour [attacher vos instances au vRack](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#instance-integration). - -Prenez note des adresses de vos instances dans votre réseau avec la commande suivante : - -```bash -openstack server list -``` - -Vous devez maintenant configurer vos instances pour qu'elles aient leurs adresses IP configurées sur leur interfaces. - -#### Créer votre Load Balancer - -Vous pouvez consulter la liste des différents types de Load Balancer que nous offrons avec cette commande : - -```bash -openstack loadbalancer flavor list -``` - -Vous pouvez maintenant créer votre Load Balancer avec la commande suivante. Dans cet exemple, nous allons faire un Load Balancer de type « Small ». - -```bash -openstack loadbalancer create --name my_load_balancer --flavor small --vip-subnet-id my_subnet -``` - -Votre Load Balancer sera configuré avec une adresse IP dans le réseau privé. Si vous souhaitez avoir un accès depuis Internet, il vous faudra attacher une adresse Floating IP. - -#### Attacher une adresse Floating IP à un Load Balancer - -Voici comment attacher une adresse Floating IP à un Load Balancer. - -```bash -openstack floating ip create Ext-Net -openstack floating ip set --port -``` - -> [!primary] -> -> Pour récupérer l'identifiant du port VIP de votre Load Balancer, utilisez `openstack loadbalancer show my_load_balancer`. - -#### Configurer votre Load Balancer - -Dans cet exemple, nous ferons juste un Load Balancer HTTP. Pour ce faire, il faut tout d'abord créer un Listener qui permettra d'écouter sur le port 80 du Load Balancer, avec cette commande : - -```bash -openstack loadbalancer listener create --name my_listener_http --protocol HTTP --protocol-port 80 my_loadbalancer -``` - -Une fois le Listener créé, il faut lui ajouter les différentes instances qui pourront répondre aux requêtes des clients. Pour ce faire, vous devez créer un Pool d'instances : - -```bash -openstack loadbalancer pool create --name my_pool_http --lb-algorithm ROUND_ROBIN --listener my_listener --protocol HTTP -``` - -Ajoutez vos instances au Pool : - -```bash -openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool -openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool -``` - -/// +>> Vous allez être redirigé vers la page qui liste les Load Balancers. Parmi les attributs qui s'affichent, les `Operating status` et `Provisioning status` fournissent des informations sur l'état de votre load balancer. Retrouvez plus d'informations sur la page « [Concepts du Load Balancer](/pages/public_cloud/public_cloud_network_services/concepts-03-loadbalancer#operating-provisioning-status) ». +>> +> Via la CLI OpenStack +>> Une autre façon de créer un Load Balancer est d'utiliser l'interface de ligne de commande d'OpenStack. Avant de commencer, consultez les guides suivants : +>> +>> - [Préparer l’environnement pour utiliser l’API OpenStack](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api). +>> - [Charger les variables d’environnement OpenStack](/pages/public_cloud/public_cloud_cross_functional/loading_openstack_environment_variables). +>> +>> **Configurer votre réseau privé** +>> +>> Avant de commencer à utiliser un Load Balancer, il vous faut créer un réseau privé : +>> +>> ```bash +>> openstack network create my_network +>> +>> openstack subnet create my_subnet --subnet-range --network my_network --no-dhcp +>> +>> openstack router create my_router +>> +>> openstack router add subnet my_router my_subnet +>> +>> openstack router set --external-gateway Ext-Net my_router +>> ``` +>> +>> Vous pouvez maintenant attacher vos instances à ce nouveau réseau. Nous vous recommandons de suivre la documentation pour [attacher vos instances au vRack](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#instance-integration). +>> +>> Prenez note des adresses de vos instances dans votre réseau avec la commande suivante : +>> +>> ```bash +>> openstack server list +>> ``` +>> +>> Vous devez maintenant configurer vos instances pour qu'elles aient leurs adresses IP configurées sur leur interfaces. +>> +>> **Créer votre Load Balancer** +>> +>> Vous pouvez consulter la liste des différents types de Load Balancer que nous offrons avec cette commande : +>> +>> ```bash +>> openstack loadbalancer flavor list +>> ``` +>> +>> Vous pouvez maintenant créer votre Load Balancer avec la commande suivante. Dans cet exemple, nous allons faire un Load Balancer de type « Small ». +>> +>> ```bash +>> openstack loadbalancer create --name my_load_balancer --flavor small --vip-subnet-id my_subnet +>> ``` +>> +>> Votre Load Balancer sera configuré avec une adresse IP dans le réseau privé. Si vous souhaitez avoir un accès depuis Internet, il vous faudra attacher une adresse Floating IP. +>> +>> **Attacher une adresse Floating IP à un Load Balancer** +>> +>> Voici comment attacher une adresse Floating IP à un Load Balancer. +>> +>> ```bash +>> openstack floating ip create Ext-Net +>> openstack floating ip set --port +>> ``` +>> +>> > [!primary] +>> > +>> > Pour récupérer l'identifiant du port VIP de votre Load Balancer, utilisez `openstack loadbalancer show my_load_balancer`. +>> > +>> +>> **Configurer votre Load Balancer** +>> +>> Dans cet exemple, nous ferons juste un Load Balancer HTTP. Pour ce faire, il faut tout d'abord créer un Listener qui permettra d'écouter sur le port 80 du Load Balancer, avec cette commande : +>> +>> ```bash +>> openstack loadbalancer listener create --name my_listener_http --protocol HTTP --protocol-port 80 my_loadbalancer +>> ``` +>> +>> Une fois le Listener créé, il faut lui ajouter les différentes instances qui pourront répondre aux requêtes des clients. Pour ce faire, vous devez créer un Pool d'instances : +>> +>> ```bash +>> openstack loadbalancer pool create --name my_pool_http --lb-algorithm ROUND_ROBIN --listener my_listener --protocol HTTP +>> ``` +>> +>> Ajoutez vos instances au Pool : +>> +>> ```bash +>> openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool +>> openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool +>> ``` +>> Vous pouvez maintenant accéder à votre Load Balancer via l'adresse Floating IP ou l'adresse IP privée depuis une instance dans votre réseau privé. diff --git a/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.fr-fr.md b/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.fr-fr.md index 5b3d122070d..5e313477170 100644 --- a/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.fr-fr.md +++ b/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.fr-fr.md @@ -1,23 +1,9 @@ --- title: Premiers pas avec le service Load Balancer pour Public Cloud excerpt: Découvrez comment débuter avec un Load Balancer Public Cloud -updated: 2025-04-28 +updated: 2025-11-03 --- - - ## Objectif Notre Load Balancer Public Cloud est basé sur le service [Openstack Octavia](https://wiki.openstack.org/wiki/Octavia) et est entièrement intégré dans l'univers Public Cloud. @@ -32,55 +18,53 @@ Notre Load Balancer Public Cloud est basé sur le service [Openstack Octavia](ht - Un Load Balancer nécessite un sous-réseau, lisez [ce guide](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack) pour plus d'informations - (Facultatif) : Ce guide explique la configuration du load balancer via l'interface graphique et l'interface en ligne de commande. Si vous souhaitez utiliser cette dernière, installez [l'environnement en ligne de commande OpenStack](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api) - ## En pratique -### Création du Load Balancer depuis votre espace client OVHcloud - -/// details | Dépliez cette section - -> [!success] -> Cliquez sur les onglets ci-dessous pour visualiser chacune des 6 étapes. +### Création du Load Balancer > [!tabs] ->> +> Via l'espace client OVHcloud >> Connectez-vous à l’[espace client OVHcloud](/links/manager), rendez-vous dans la section `Public Cloud`{.action} et sélectionnez le projet Public Cloud concerné. Cliquez sur `Load Balancer`{.action} (sous **Network**) dans le menu de gauche, puis cliquez sur le bouton `Créer un Load Balancer`{.action}. >> >> La page de configuration s'ouvre. >> -> **Étape 1 : Choix de la taille** +>> **Étape 1 : Choix de la région** >> ->> ![Choix de la taille](images/size.png){.thumbnail} +>> ![Choix de la région](images/region.png){.thumbnail} >> ->> L'interface contient un lien vers notre site sur lequel les caractéristiques / benchmark de toutes tailles sont fournies. Une fois que vous avez choisi votre taille, cliquez sur `Suivant`{.action}. +>> 1. **Sélectionnez le type de zone :** >> +>> - 1AZ : Déploiement sur une seule zone de disponibilité. +>> - 3AZ : Déploiement réparti sur trois zones pour une haute disponibilité. >> -> **Étape 2 : Choix de la région** +>> 2. **Choisissez la région :** Seules les régions sur lesquelles vous avez un réseau privé et au moins un sous-réseau peuvent être sélectionnées. Sélectionnez la région et cliquez sur `Suivant`{.action}. >> ->> ![Choix de la région](images/region.png){.thumbnail} +>> **Étape 2 : Choix de la taille** +>> +>> ![Choix de la taille](images/size.png){.thumbnail} >> ->> Seules les régions sur lesquelles vous avez un réseau privé et au moins un sous-réseau peuvent être sélectionnées. Sélectionnez la région et cliquez sur `Suivant`{.action}. +>> L'interface contient un lien vers notre site sur lequel les caractéristiques et un benchmark de toutes les tailles sont fournis. Une fois que vous avez choisi votre taille, cliquez sur `Suivant`{.action}. >> -> **Étape 3 : attacher une IP publique (ou non)** +>> **Étape 3 : Attacher une IP publique (ou non)** >> >> ![Public IP choice](images/floating_IP.png){.thumbnail} >> ->> À ce stade, vous devez savoir si votre Load Balancer recevra du trafic public ou non (pour plus de détails, consultez notre page « [Concepts - Réseau Public Cloud](/pages/public_cloud/public_cloud_network_services/concepts-01-public-cloud-networking-concepts)) ». +>> À ce stade, vous devez savoir si votre Load Balancer recevra du trafic public ou non (pour plus de détails, consultez notre page « [Concepts - Réseau Public Cloud](/pages/public_cloud/public_cloud_network_services/concepts-01-public-cloud-networking-concepts)) ». >> >> Si votre Load Balancer reçoit du trafic public, vous disposez de 2 options : >> ->> - `Nouvelle IP Publique` : cette option créera une nouvelle adresse Floating IP pour votre Load Balancer. +>> - `Nouvelle IP Publique` : Cette option créera une nouvelle adresse Floating IP pour votre Load Balancer. >> - Si vous avez déjà une adresse Floating IP, l'interface vous proposera d'en choisir une. >> ->> Si votre Load Balancer ne doit recevoir que du trafic privé, choisissez « Aucune IP publique ». +>> Si votre Load Balancer ne doit recevoir que du trafic privé, choisissez `Aucune IP publique`{.action}. >> -> **Étape 4 : sélectionnez le réseau privé et le sous-réseau sur lesquels le Load Balancer sera créé** +>> **Étape 4 : Sélectionner le réseau privé et le sous-réseau sur lesquels le Load Balancer sera créé** >> >> ![Choix du réseau](images/private_network.png){.thumbnail} >> >> L'interface vous informera si le réseau privé ou le sous-réseau ne sont pas conformes aux prérequis (voir notre page « [Concepts - Load Balancer](/pages/public_cloud/public_cloud_network_services/concepts-03-loadbalancer#network-prerequisites) »). >> -> **Étape 5 (facultatif) : définir le ou les listeners et les membres** +>> **Étape 5 (facultatif) : Définir le ou les listeners et les membres** >> >> ![Choix du listener](images/listener.png){.thumbnail} >> @@ -89,108 +73,101 @@ Notre Load Balancer Public Cloud est basé sur le service [Openstack Octavia](ht >> - Enfin, parmi les instances de votre région, choisissez l'IP et le port membre qui feront partie du pool. Notez que pour simplifier le processus de configuration, votre pool doit avoir le même protocole que le listener, et que le membre ne peut être choisi qu'à partir de l'instance. Ces limitations peuvent être contournées en ignorant cette partie de la configuration et en utilisant la configuration du pool/membre une fois le Load Balancer créé. >> >> > [!primary] ->> > >> > Pour simplifier le processus de configuration, votre pool doit avoir le même protocole que le listener et le membre ne peut être choisi qu'à partir d'une instance. De plus, l'algorithme de load balancing par défaut est : `ROUND_ROBIN`. >> > Ces limitations peuvent être contournées en ignorant cette partie de la configuration et en utilisant la configuration du pool/membre une fois le Load Balancer créé. >> > >> -> **Étape 6 : Définir le nom du Load Balancer** +>> **Étape 6 : Définir le nom du Load Balancer** >> >> ![Name](images/name.png){.thumbnail} >> >> Vous pouvez définir un nom pour le Load Balancer et cliquer sur `Créer un Load Balancer`{.action}. >> ->> Vous allez être redirigé vers la page qui liste les Load Balancers. Parmi les attributs qui s'affichent, les `Operating status` et `Provisioning status` fournissent des informations sur l'état de votre load balancer. Retrouvez plus d'informations sur la [page Concepts du Load Balancer](/pages/public_cloud/public_cloud_network_services/concepts-03-loadbalancer#operating-provisioning-status). ->> - -/// - -### Création du Load Balancer via l'interface en ligne de commande (CLI) Openstack - -/// details | Dépliez cette section - -Une autre façon de créer un Load Balance est d'utiliser l'interface de ligne de commande d'Openstack. Avant de commencer, consultez les guides suivants : - -[Preparing an environment for using the OpenStack API](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api).
-[Setting OpenStack environment variables](/pages/public_cloud/public_cloud_cross_functional/loading_openstack_environment_variables). - -#### Configurer votre réseau privé - -Avant de commencer à utiliser un Load Balancer, il vous faut créer un réseau privé : - -```bash -openstack network create my_network - -openstack subnet create my_subnet --subnet-range --network my_network --no-dhcp - -openstack router create my_router - -openstack router add subnet my_router my_subnet - -openstack router set --external-gateway Ext-Net my_router -``` - -Vous pouvez maintenant attacher vos instances à ce nouveau réseau. Nous vous recommandons de suivre la documentation pour [attacher vos instances au vRack](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#instance-integration). - -Prenez note des adresses de vos instances dans votre réseau avec la commande suivante : - -```bash -openstack server list -``` - -Vous devez maintenant configurer vos instances pour qu'elles aient leurs adresses IP configurées sur leur interfaces. - -#### Créer votre Load Balancer - -Vous pouvez consulter la liste des différents types de Load Balancer que nous offrons avec cette commande : - -```bash -openstack loadbalancer flavor list -``` - -Vous pouvez maintenant créer votre Load Balancer avec la commande suivante. Dans cet exemple, nous allons faire un Load Balancer de type « Small ». - -```bash -openstack loadbalancer create --name my_load_balancer --flavor small --vip-subnet-id my_subnet -``` - -Votre Load Balancer sera configuré avec une adresse IP dans le réseau privé. Si vous souhaitez avoir un accès depuis Internet, il vous faudra attacher une adresse Floating IP. - -#### Attacher une adresse Floating IP à un Load Balancer - -Voici comment attacher une adresse Floating IP à un Load Balancer. - -```bash -openstack floating ip create Ext-Net -openstack floating ip set --port -``` - -> [!primary] -> -> Pour récupérer l'identifiant du port VIP de votre Load Balancer, utilisez `openstack loadbalancer show my_load_balancer`. - -#### Configurer votre Load Balancer - -Dans cet exemple, nous ferons juste un Load Balancer HTTP. Pour ce faire, il faut tout d'abord créer un Listener qui permettra d'écouter sur le port 80 du Load Balancer, avec cette commande : - -```bash -openstack loadbalancer listener create --name my_listener_http --protocol HTTP --protocol-port 80 my_loadbalancer -``` - -Une fois le Listener créé, il faut lui ajouter les différentes instances qui pourront répondre aux requêtes des clients. Pour ce faire, vous devez créer un Pool d'instances : - -```bash -openstack loadbalancer pool create --name my_pool_http --lb-algorithm ROUND_ROBIN --listener my_listener --protocol HTTP -``` - -Ajoutez vos instances au Pool : - -```bash -openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool -openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool -``` - -/// +>> Vous allez être redirigé vers la page qui liste les Load Balancers. Parmi les attributs qui s'affichent, les `Operating status` et `Provisioning status` fournissent des informations sur l'état de votre load balancer. Retrouvez plus d'informations sur la page « [Concepts du Load Balancer](/pages/public_cloud/public_cloud_network_services/concepts-03-loadbalancer#operating-provisioning-status) ». +>> +> Via la CLI OpenStack +>> Une autre façon de créer un Load Balancer est d'utiliser l'interface de ligne de commande d'OpenStack. Avant de commencer, consultez les guides suivants : +>> +>> - [Préparer l’environnement pour utiliser l’API OpenStack](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api). +>> - [Charger les variables d’environnement OpenStack](/pages/public_cloud/public_cloud_cross_functional/loading_openstack_environment_variables). +>> +>> **Configurer votre réseau privé** +>> +>> Avant de commencer à utiliser un Load Balancer, il vous faut créer un réseau privé : +>> +>> ```bash +>> openstack network create my_network +>> +>> openstack subnet create my_subnet --subnet-range --network my_network --no-dhcp +>> +>> openstack router create my_router +>> +>> openstack router add subnet my_router my_subnet +>> +>> openstack router set --external-gateway Ext-Net my_router +>> ``` +>> +>> Vous pouvez maintenant attacher vos instances à ce nouveau réseau. Nous vous recommandons de suivre la documentation pour [attacher vos instances au vRack](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#instance-integration). +>> +>> Prenez note des adresses de vos instances dans votre réseau avec la commande suivante : +>> +>> ```bash +>> openstack server list +>> ``` +>> +>> Vous devez maintenant configurer vos instances pour qu'elles aient leurs adresses IP configurées sur leur interfaces. +>> +>> **Créer votre Load Balancer** +>> +>> Vous pouvez consulter la liste des différents types de Load Balancer que nous offrons avec cette commande : +>> +>> ```bash +>> openstack loadbalancer flavor list +>> ``` +>> +>> Vous pouvez maintenant créer votre Load Balancer avec la commande suivante. Dans cet exemple, nous allons faire un Load Balancer de type « Small ». +>> +>> ```bash +>> openstack loadbalancer create --name my_load_balancer --flavor small --vip-subnet-id my_subnet +>> ``` +>> +>> Votre Load Balancer sera configuré avec une adresse IP dans le réseau privé. Si vous souhaitez avoir un accès depuis Internet, il vous faudra attacher une adresse Floating IP. +>> +>> **Attacher une adresse Floating IP à un Load Balancer** +>> +>> Voici comment attacher une adresse Floating IP à un Load Balancer. +>> +>> ```bash +>> openstack floating ip create Ext-Net +>> openstack floating ip set --port +>> ``` +>> +>> > [!primary] +>> > +>> > Pour récupérer l'identifiant du port VIP de votre Load Balancer, utilisez `openstack loadbalancer show my_load_balancer`. +>> > +>> +>> **Configurer votre Load Balancer** +>> +>> Dans cet exemple, nous ferons juste un Load Balancer HTTP. Pour ce faire, il faut tout d'abord créer un Listener qui permettra d'écouter sur le port 80 du Load Balancer, avec cette commande : +>> +>> ```bash +>> openstack loadbalancer listener create --name my_listener_http --protocol HTTP --protocol-port 80 my_loadbalancer +>> ``` +>> +>> Une fois le Listener créé, il faut lui ajouter les différentes instances qui pourront répondre aux requêtes des clients. Pour ce faire, vous devez créer un Pool d'instances : +>> +>> ```bash +>> openstack loadbalancer pool create --name my_pool_http --lb-algorithm ROUND_ROBIN --listener my_listener --protocol HTTP +>> ``` +>> +>> Ajoutez vos instances au Pool : +>> +>> ```bash +>> openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool +>> openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool +>> ``` +>> Vous pouvez maintenant accéder à votre Load Balancer via l'adresse Floating IP ou l'adresse IP privée depuis une instance dans votre réseau privé. diff --git a/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.it-it.md b/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.it-it.md index 7baf1c4aac6..1fa20d549eb 100644 --- a/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.it-it.md +++ b/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.it-it.md @@ -1,23 +1,9 @@ --- -title: Getting started with Load Balancer on Public Cloud (EN) +title: Getting started with Load Balancer on Public Cloud excerpt: Discover how to launch a Load Balancer on Public Cloud -updated: 2025-04-28 +updated: 2025-11-03 --- - - ## Objective Our Public Cloud Load Balancer is based on [OpenStack Octavia](https://wiki.openstack.org/wiki/Octavia) and is fully integrated into the Public Cloud universe. @@ -34,152 +20,156 @@ Our Public Cloud Load Balancer is based on [OpenStack Octavia](https://wiki.ope ## Instructions -### Creating the Load Balancer from the OVHcloud Control Panel - -Log in to the [OVHcloud Control Panel](/links/manager), go to the `Public Cloud`{.action} section and select the Public Cloud project concerned. 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). - -### Creating the Load Balancer from the Openstack Command Line Interface - -/// details | Unfold this section - -Another way to create a Load Balancer is through the Openstack Command Line Interface. Before you begin, consult the following guides: - -[Preparing an environment for using the OpenStack API](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api).
-[Setting OpenStack environment variables](/pages/public_cloud/public_cloud_cross_functional/loading_openstack_environment_variables). - -#### Configuring your private network - -Before creating a Load Balancer, you will need to set up a private network: - -```bash -openstack network create my_network - -openstack subnet create my_subnet --subnet-range --network my_network --no-dhcp - -openstack router create my_router - -openstack router add subnet my_router my_subnet - -openstack router set --external-gateway Ext-Net my_router -``` - -You can now attach your instances to the new network. We recommend following our guide to [integrate an instance into vRack](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#instance-integration). List the addresses of your instances in your network with the following command: - -```bash -openstack server list -``` - -In the next step, configure the network interfaces of your instances according to this output. - -#### Creating the Load Balancer - -You can view a list of the different Load Balancer flavors we offer with this command: - -```bash -openstack loadbalancer flavor list -``` - -You can now create your Load Balancer with the following command. In this example, we will create a "Small" Load Balancer. - -```bash -openstack loadbalancer create --name my_load_balancer --flavor small --vip-subnet-id my_subnet -``` - -Your Load Balancer will be configured with an IP address of the private network. If you want to have access from the internet, you will need to attach a Floating IP address. - -#### Attaching a Floating IP address to a Load Balancer - -This is how to attach a Floating IP address to a Load Balancer: - -```bash -openstack floating ip create Ext-Net -openstack floating ip set --port -``` - -> [!primary] -> -> To retrieve the VIP port ID of your Load Balancer, use `openstack loadbalancer show my_load_balancer`. - -#### Configuring your Load Balancer - -In this example we will configure an HTTP Load Balancer. In order to listen on port 80 of the Load Balancer, create a Listener with this command: - -```bash -openstack loadbalancer listener create --name my_listener_http --protocol HTTP --protocol-port 80 my_loadbalancer -``` - -Once the Listener has been created, you need to add each instance that can respond to external requests. To do this, you must create an Instance Pool: - -```bash -openstack loadbalancer pool create --name my_pool_http --lb-algorithm ROUND_ROBIN --listener my_listener --protocol HTTP -``` - -Add your instances to the Instance Pool: - -```bash -openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool -openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool -``` - -You can now access your Load Balancer via the Floating IP or private IP address from an instance in your private network. - -/// +### Creating the Load Balancer + +> [!tabs] +> Via the OVHcloud Control Panel +>> Log in to the [OVHcloud Control Panel](/links/manager), go to the `Public Cloud`{.action} section and select the Public Cloud project concerned. 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: Region choice** +>> +>> ![Region choice](images/region.png){.thumbnail} +>> +>> 1. **Select the zone type:** +>> +>> - 1AZ: Deployment in a single availability zone. +>> - 3AZ: Deployment spread across three availability zones for high availability. +>> +>> 2. **Choose the region:** Only regions where you have a private network and at least one subnet can be selected. Select the region and click `Next`{.action}. +>> +>> **Step 2: 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 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`{.action}. +>> +>> **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](/pages/public_cloud/public_cloud_network_services/concepts-03-loadbalancer#operating-provisioning-status)" page. +>> +> Via the OpenStack CLI +>> Another way to create a Load Balancer is through the OpenStack Command Line Interface. Before you begin, consult the following guides: +>> +>> - [Preparing an environment for using the OpenStack API](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api). +>> - [Setting OpenStack environment variables](/pages/public_cloud/public_cloud_cross_functional/loading_openstack_environment_variables). +>> +>> **Configuring your private network** +>> +>> Before creating a Load Balancer, you will need to set up a private network: +>> +>> ```bash +>> openstack network create my_network +>> +>> openstack subnet create my_subnet --subnet-range --network my_network --no-dhcp +>> +>> openstack router create my_router +>> +>> openstack router add subnet my_router my_subnet +>> +>> openstack router set --external-gateway Ext-Net my_router +>> ``` +>> +>> You can now attach your instances to the new network. We recommend following our guide to [integrate an instance into vRack](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#instance-integration). +>> +>> List the addresses of your instances in your network with the following command: +>> +>> ```bash +>> openstack server list +>> ``` +>> +>> In the next step, configure the network interfaces of your instances according to this output. +>> +>> **Creating the Load Balancer** +>> +>> You can view a list of the different Load Balancer flavors we offer with this command: +>> +>> ```bash +>> openstack loadbalancer flavor list +>> ``` +>> +>> You can now create your Load Balancer with the following command. In this example, we will create a "Small" Load Balancer. +>> +>> ```bash +>> openstack loadbalancer create --name my_load_balancer --flavor small --vip-subnet-id my_subnet +>> ``` +>> +>> Your Load Balancer will be configured with an IP address of the private network. If you want to have access from the internet, you will need to attach a Floating IP address. +>> +>> **Attaching a Floating IP address to a Load Balancer** +>> +>> This is how to attach a Floating IP address to a Load Balancer: +>> +>> ```bash +>> openstack floating ip create Ext-Net +>> openstack floating ip set --port +>> ``` +>> +>> > [!primary] +>> > +>> > To retrieve the VIP port ID of your Load Balancer, use `openstack loadbalancer show my_load_balancer`. +>> > +>> +>> **Configuring your Load Balancer** +>> +>> In this example we will configure an HTTP Load Balancer. In order to listen on port 80 of the Load Balancer, create a Listener with this command: +>> +>> ```bash +>> openstack loadbalancer listener create --name my_listener_http --protocol HTTP --protocol-port 80 my_loadbalancer +>> ``` +>> +>> Once the Listener has been created, you need to add each instance that can respond to external requests. To do this, you must create an Instance Pool: +>> +>> ```bash +>> openstack loadbalancer pool create --name my_pool_http --lb-algorithm ROUND_ROBIN --listener my_listener --protocol HTTP +>> ``` +>> +>> Add your instances to the Instance Pool: +>> +>> ```bash +>> openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool +>> openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool +>> ``` +>> +>> You can now access your Load Balancer via the Floating IP or private IP address from an instance in your private network. +>> ## Go further diff --git a/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.pl-pl.md b/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.pl-pl.md index 7baf1c4aac6..1fa20d549eb 100644 --- a/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.pl-pl.md +++ b/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.pl-pl.md @@ -1,23 +1,9 @@ --- -title: Getting started with Load Balancer on Public Cloud (EN) +title: Getting started with Load Balancer on Public Cloud excerpt: Discover how to launch a Load Balancer on Public Cloud -updated: 2025-04-28 +updated: 2025-11-03 --- - - ## Objective Our Public Cloud Load Balancer is based on [OpenStack Octavia](https://wiki.openstack.org/wiki/Octavia) and is fully integrated into the Public Cloud universe. @@ -34,152 +20,156 @@ Our Public Cloud Load Balancer is based on [OpenStack Octavia](https://wiki.ope ## Instructions -### Creating the Load Balancer from the OVHcloud Control Panel - -Log in to the [OVHcloud Control Panel](/links/manager), go to the `Public Cloud`{.action} section and select the Public Cloud project concerned. 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). - -### Creating the Load Balancer from the Openstack Command Line Interface - -/// details | Unfold this section - -Another way to create a Load Balancer is through the Openstack Command Line Interface. Before you begin, consult the following guides: - -[Preparing an environment for using the OpenStack API](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api).
-[Setting OpenStack environment variables](/pages/public_cloud/public_cloud_cross_functional/loading_openstack_environment_variables). - -#### Configuring your private network - -Before creating a Load Balancer, you will need to set up a private network: - -```bash -openstack network create my_network - -openstack subnet create my_subnet --subnet-range --network my_network --no-dhcp - -openstack router create my_router - -openstack router add subnet my_router my_subnet - -openstack router set --external-gateway Ext-Net my_router -``` - -You can now attach your instances to the new network. We recommend following our guide to [integrate an instance into vRack](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#instance-integration). List the addresses of your instances in your network with the following command: - -```bash -openstack server list -``` - -In the next step, configure the network interfaces of your instances according to this output. - -#### Creating the Load Balancer - -You can view a list of the different Load Balancer flavors we offer with this command: - -```bash -openstack loadbalancer flavor list -``` - -You can now create your Load Balancer with the following command. In this example, we will create a "Small" Load Balancer. - -```bash -openstack loadbalancer create --name my_load_balancer --flavor small --vip-subnet-id my_subnet -``` - -Your Load Balancer will be configured with an IP address of the private network. If you want to have access from the internet, you will need to attach a Floating IP address. - -#### Attaching a Floating IP address to a Load Balancer - -This is how to attach a Floating IP address to a Load Balancer: - -```bash -openstack floating ip create Ext-Net -openstack floating ip set --port -``` - -> [!primary] -> -> To retrieve the VIP port ID of your Load Balancer, use `openstack loadbalancer show my_load_balancer`. - -#### Configuring your Load Balancer - -In this example we will configure an HTTP Load Balancer. In order to listen on port 80 of the Load Balancer, create a Listener with this command: - -```bash -openstack loadbalancer listener create --name my_listener_http --protocol HTTP --protocol-port 80 my_loadbalancer -``` - -Once the Listener has been created, you need to add each instance that can respond to external requests. To do this, you must create an Instance Pool: - -```bash -openstack loadbalancer pool create --name my_pool_http --lb-algorithm ROUND_ROBIN --listener my_listener --protocol HTTP -``` - -Add your instances to the Instance Pool: - -```bash -openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool -openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool -``` - -You can now access your Load Balancer via the Floating IP or private IP address from an instance in your private network. - -/// +### Creating the Load Balancer + +> [!tabs] +> Via the OVHcloud Control Panel +>> Log in to the [OVHcloud Control Panel](/links/manager), go to the `Public Cloud`{.action} section and select the Public Cloud project concerned. 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: Region choice** +>> +>> ![Region choice](images/region.png){.thumbnail} +>> +>> 1. **Select the zone type:** +>> +>> - 1AZ: Deployment in a single availability zone. +>> - 3AZ: Deployment spread across three availability zones for high availability. +>> +>> 2. **Choose the region:** Only regions where you have a private network and at least one subnet can be selected. Select the region and click `Next`{.action}. +>> +>> **Step 2: 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 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`{.action}. +>> +>> **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](/pages/public_cloud/public_cloud_network_services/concepts-03-loadbalancer#operating-provisioning-status)" page. +>> +> Via the OpenStack CLI +>> Another way to create a Load Balancer is through the OpenStack Command Line Interface. Before you begin, consult the following guides: +>> +>> - [Preparing an environment for using the OpenStack API](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api). +>> - [Setting OpenStack environment variables](/pages/public_cloud/public_cloud_cross_functional/loading_openstack_environment_variables). +>> +>> **Configuring your private network** +>> +>> Before creating a Load Balancer, you will need to set up a private network: +>> +>> ```bash +>> openstack network create my_network +>> +>> openstack subnet create my_subnet --subnet-range --network my_network --no-dhcp +>> +>> openstack router create my_router +>> +>> openstack router add subnet my_router my_subnet +>> +>> openstack router set --external-gateway Ext-Net my_router +>> ``` +>> +>> You can now attach your instances to the new network. We recommend following our guide to [integrate an instance into vRack](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#instance-integration). +>> +>> List the addresses of your instances in your network with the following command: +>> +>> ```bash +>> openstack server list +>> ``` +>> +>> In the next step, configure the network interfaces of your instances according to this output. +>> +>> **Creating the Load Balancer** +>> +>> You can view a list of the different Load Balancer flavors we offer with this command: +>> +>> ```bash +>> openstack loadbalancer flavor list +>> ``` +>> +>> You can now create your Load Balancer with the following command. In this example, we will create a "Small" Load Balancer. +>> +>> ```bash +>> openstack loadbalancer create --name my_load_balancer --flavor small --vip-subnet-id my_subnet +>> ``` +>> +>> Your Load Balancer will be configured with an IP address of the private network. If you want to have access from the internet, you will need to attach a Floating IP address. +>> +>> **Attaching a Floating IP address to a Load Balancer** +>> +>> This is how to attach a Floating IP address to a Load Balancer: +>> +>> ```bash +>> openstack floating ip create Ext-Net +>> openstack floating ip set --port +>> ``` +>> +>> > [!primary] +>> > +>> > To retrieve the VIP port ID of your Load Balancer, use `openstack loadbalancer show my_load_balancer`. +>> > +>> +>> **Configuring your Load Balancer** +>> +>> In this example we will configure an HTTP Load Balancer. In order to listen on port 80 of the Load Balancer, create a Listener with this command: +>> +>> ```bash +>> openstack loadbalancer listener create --name my_listener_http --protocol HTTP --protocol-port 80 my_loadbalancer +>> ``` +>> +>> Once the Listener has been created, you need to add each instance that can respond to external requests. To do this, you must create an Instance Pool: +>> +>> ```bash +>> openstack loadbalancer pool create --name my_pool_http --lb-algorithm ROUND_ROBIN --listener my_listener --protocol HTTP +>> ``` +>> +>> Add your instances to the Instance Pool: +>> +>> ```bash +>> openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool +>> openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool +>> ``` +>> +>> You can now access your Load Balancer via the Floating IP or private IP address from an instance in your private network. +>> ## Go further diff --git a/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.pt-pt.md b/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.pt-pt.md index 8b70811c8f9..1fa20d549eb 100644 --- a/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.pt-pt.md +++ b/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/guide.pt-pt.md @@ -1,23 +1,9 @@ --- -title: Getting started with Load Balancer on Public Cloud (EN) +title: Getting started with Load Balancer on Public Cloud excerpt: Discover how to launch a Load Balancer on Public Cloud -updated: 2025-04-28 +updated: 2025-11-03 --- - - ## Objective Our Public Cloud Load Balancer is based on [OpenStack Octavia](https://wiki.openstack.org/wiki/Octavia) and is fully integrated into the Public Cloud universe. @@ -34,152 +20,156 @@ Our Public Cloud Load Balancer is based on [OpenStack Octavia](https://wiki.ope ## Instructions -### Creating the Load Balancer from the OVHcloud Control Panel - -Log in to the [OVHcloud Control Panel](/links/manager), go to the `Public Cloud`{.action} section and select the Public Cloud project concerned. 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). - -### Creating the Load Balancer from the Openstack Command Line Interface - -/// details | Unfold this section - -Another way to create a Load Balancer is through the Openstack Command Line Interface. Before you begin, consult the following guides: - -[Preparing an environment for using the OpenStack API](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api).
-[Setting OpenStack environment variables](/pages/public_cloud/public_cloud_cross_functional/loading_openstack_environment_variables). - -#### Configuring your private network - -Before creating a Load Balancer, you will need to set up a private network: - -```bash -openstack network create my_network - -openstack subnet create my_subnet --subnet-range --network my_network --no-dhcp - -openstack router create my_router - -openstack router add subnet my_router my_subnet - -openstack router set --external-gateway Ext-Net my_router -``` - -You can now attach your instances to the new network. We recommend following our guide to [integrate an instance into vRack](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#instance-integration). List the addresses of your instances in your network with the following command: - -```bash -openstack server list -``` - -In the next step, configure the network interfaces of your instances according to this output. - -#### Creating the Load Balancer - -You can view a list of the different Load Balancer flavors we offer with this command: - -```bash -openstack loadbalancer flavor list -``` - -You can now create your Load Balancer with the following command. In this example, we will create a "Small" Load Balancer. - -```bash -openstack loadbalancer create --name my_load_balancer --flavor small --vip-subnet-id my_subnet -``` - -Your Load Balancer will be configured with an IP address of the private network. If you want to have access from the internet, you will need to attach a Floating IP address. - -#### Attaching a Floating IP address to a Load Balancer - -This is how to attach a Floating IP address to a Load Balancer: - -```bash -openstack floating ip create Ext-Net -openstack floating ip set --port -``` - -> [!primary] -> -> To retrieve the VIP port ID of your Load Balancer, use `openstack loadbalancer show my_load_balancer`. - -#### Configuring your Load Balancer - -In this example we will configure an HTTP Load Balancer. In order to listen on port 80 of the Load Balancer, create a Listener with this command: - -```bash -openstack loadbalancer listener create --name my_listener_http --protocol HTTP --protocol-port 80 my_loadbalancer -``` - -Once the Listener has been created, you need to add each instance that can respond to external requests. To do this, you must create an Instance Pool: - -```bash -openstack loadbalancer pool create --name my_pool_http --lb-algorithm ROUND_ROBIN --listener my_listener --protocol HTTP -``` - -Add your instances to the Instance Pool: - -```bash -openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool -openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool -``` - -You can now access your Load Balancer via the Floating IP or private IP address from an instance in your private network. - -/// +### Creating the Load Balancer + +> [!tabs] +> Via the OVHcloud Control Panel +>> Log in to the [OVHcloud Control Panel](/links/manager), go to the `Public Cloud`{.action} section and select the Public Cloud project concerned. 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: Region choice** +>> +>> ![Region choice](images/region.png){.thumbnail} +>> +>> 1. **Select the zone type:** +>> +>> - 1AZ: Deployment in a single availability zone. +>> - 3AZ: Deployment spread across three availability zones for high availability. +>> +>> 2. **Choose the region:** Only regions where you have a private network and at least one subnet can be selected. Select the region and click `Next`{.action}. +>> +>> **Step 2: 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 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`{.action}. +>> +>> **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](/pages/public_cloud/public_cloud_network_services/concepts-03-loadbalancer#operating-provisioning-status)" page. +>> +> Via the OpenStack CLI +>> Another way to create a Load Balancer is through the OpenStack Command Line Interface. Before you begin, consult the following guides: +>> +>> - [Preparing an environment for using the OpenStack API](/pages/public_cloud/public_cloud_cross_functional/prepare_the_environment_for_using_the_openstack_api). +>> - [Setting OpenStack environment variables](/pages/public_cloud/public_cloud_cross_functional/loading_openstack_environment_variables). +>> +>> **Configuring your private network** +>> +>> Before creating a Load Balancer, you will need to set up a private network: +>> +>> ```bash +>> openstack network create my_network +>> +>> openstack subnet create my_subnet --subnet-range --network my_network --no-dhcp +>> +>> openstack router create my_router +>> +>> openstack router add subnet my_router my_subnet +>> +>> openstack router set --external-gateway Ext-Net my_router +>> ``` +>> +>> You can now attach your instances to the new network. We recommend following our guide to [integrate an instance into vRack](/pages/public_cloud/public_cloud_network_services/getting-started-07-creating-vrack#instance-integration). +>> +>> List the addresses of your instances in your network with the following command: +>> +>> ```bash +>> openstack server list +>> ``` +>> +>> In the next step, configure the network interfaces of your instances according to this output. +>> +>> **Creating the Load Balancer** +>> +>> You can view a list of the different Load Balancer flavors we offer with this command: +>> +>> ```bash +>> openstack loadbalancer flavor list +>> ``` +>> +>> You can now create your Load Balancer with the following command. In this example, we will create a "Small" Load Balancer. +>> +>> ```bash +>> openstack loadbalancer create --name my_load_balancer --flavor small --vip-subnet-id my_subnet +>> ``` +>> +>> Your Load Balancer will be configured with an IP address of the private network. If you want to have access from the internet, you will need to attach a Floating IP address. +>> +>> **Attaching a Floating IP address to a Load Balancer** +>> +>> This is how to attach a Floating IP address to a Load Balancer: +>> +>> ```bash +>> openstack floating ip create Ext-Net +>> openstack floating ip set --port +>> ``` +>> +>> > [!primary] +>> > +>> > To retrieve the VIP port ID of your Load Balancer, use `openstack loadbalancer show my_load_balancer`. +>> > +>> +>> **Configuring your Load Balancer** +>> +>> In this example we will configure an HTTP Load Balancer. In order to listen on port 80 of the Load Balancer, create a Listener with this command: +>> +>> ```bash +>> openstack loadbalancer listener create --name my_listener_http --protocol HTTP --protocol-port 80 my_loadbalancer +>> ``` +>> +>> Once the Listener has been created, you need to add each instance that can respond to external requests. To do this, you must create an Instance Pool: +>> +>> ```bash +>> openstack loadbalancer pool create --name my_pool_http --lb-algorithm ROUND_ROBIN --listener my_listener --protocol HTTP +>> ``` +>> +>> Add your instances to the Instance Pool: +>> +>> ```bash +>> openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool +>> openstack loadbalancer member create --subnet-id my_subnet --address --protocol-port 80 my_pool +>> ``` +>> +>> You can now access your Load Balancer via the Floating IP or private IP address from an instance in your private network. +>> ## Go further @@ -191,4 +181,4 @@ If you need training or technical assistance to implement our solutions, contact Join our [community of users](/links/community). -Join our [Discord](https://discord.gg/ovhcloud) to discuss with the OVHcloud team and other users. \ No newline at end of file +Join our [Discord](https://discord.gg/ovhcloud) to discuss with the OVHcloud team and other users. diff --git a/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/images/region.png b/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/images/region.png index 53b4a126a13..a80d07334aa 100644 Binary files a/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/images/region.png and b/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/images/region.png differ diff --git a/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/images/size.png b/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/images/size.png index 2dd419ae9a5..b5c398a9569 100644 Binary files a/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/images/size.png and b/pages/public_cloud/public_cloud_network_services/getting-started-01-create-lb-service/images/size.png differ