Proofreading

Author: Y0Coss

pages/bare_metal_cloud/dedicated_servers/opennebula-deployment/guide.en-gb.md

@@ -1,14 +1,14 @@
 ---
 title: How to deploy and verify an OpenNebula Hosted Cloud on Bare Metal servers
-excerpt: Deploy a certified OpenNebula Hosted Cloud using OVHcloud bare metal servers and Ansible playbooks.
-updated: 2025-11-18
+excerpt: Deploy a certified OpenNebula Hosted Cloud using OVHcloud Bare Metal servers and Ansible playbooks.
+updated: 2025-12-09
 ---
 
 ## Introduction
 
 OpenNebula is a powerful, open-source **Cloud Management Platform** (CMP) designed to manage and provision virtualized infrastructure.
 
-Acting as an orchestrator, it turns physical infrastructure into a managed **Infrastructure as a Service** (IaaS) cloud, accessible via a unified control interface. It supports major hypervisors and allows for hybrid deployments by integrating with public cloud providers, such as OVHcloud.
+Acting as an orchestrator, it turns a physical infrastructure into a managed **Infrastructure as a Service** (IaaS) cloud, accessible via a unified control interface. It supports major hypervisors and allows for hybrid deployments by integrating with Public Cloud providers, such as OVHcloud.
 
 The deployment of OpenNebula on OVHcloud infrastructure is validated as part of the **OpenNebula Cloud-Ready Certification Program**.
 
@@ -27,12 +27,12 @@ Following this guide, you will be able to:
 
 ## Requirements
 
-- **Two** [dedicated servers](/links/bare-metal/bare-metal) from the Scale or High Grade ranges,
-- An active [vRack](/links/network/vrack) service,
-- A public block of [Additional IP](/links/network/additional-ip) addresses, sized according to your needs,
+- **Two** [dedicated servers](/links/bare-metal/bare-metal) from the Scale or High Grade ranges.
+- An active [vRack](/links/network/vrack) service.
+- A public block of [Additional IP](/links/network/additional-ip) addresses, sized according to your needs.
 - Access to the [OVHcloud Control Panel](/links/manager).
 
-> [!Primary]
+> [!primary]
 >
 > The reference OpenNebula deployment uses the following configuration:
 > 
@@ -60,46 +60,46 @@ Following this guide, you will be able to:
 
 ## Instructions
 
-### Step 1 - Setting up your OVHcloud infrastructure <a name="Infrastructure_Provisioning"></a>
+### Step 1 - Setting up your OVHcloud infrastructure <a name="infrastructure_provisioning"></a>
 
 First, you need to install Ubuntu 24.04 LTS on both of your dedicated servers, by following the instructions in [this guide](/pages/bare_metal_cloud/dedicated_servers/getting-started-with-dedicated-server).
 
-Subsequently, add both servers to your vRack service by following step 2 of [this vRack configuration guide](/pages/bare_metal_cloud/dedicated_servers/vrack_configuring_on_dedicated_server). 
+Subsequently, add both servers to your vRack service by following step 2 of [this vRack configuration guide](/pages/bare_metal_cloud/dedicated_servers/vrack_configuring_on_dedicated_server).
 
 Finally, from the OVHcloud Control Panel, open the `Network`{.action} section, then select `Public IP Addresses`{.action} under **Public Network**. Once you have reached the IP management interface, click on the `Order IPs`{.action} button near the top of the page. Choose the IP version, then **select the vRack your servers are attached to**, and the region where those servers are hosted.
 
 > [!warning]
 > 
 > **Important:** To ensure functionality, please make sure that the IP block you ordered is **routed to the vRack** attached to the servers, and not used as a classic failover configuration.
 >
-> If you are unsure or need more information, please consult the following guide : [Configuring an Additional IP block in a vRack](/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/).
+> If you are unsure or need more information, please consult the following guide: [Configuring an Additional IP block in a vRack](/pages/bare_metal_cloud/dedicated_servers/configuring-an-ip-block-in-a-vrack/).
 >
 
 ### Step 2 - Collecting the Bare Metal & Network settings
 
-Before starting the OpenNebula deployment, gather all parameters required for the automation process. **Update the inventory values** in the [Hosted Cloud OVHcloud repository](https://github.com/OpenNebula/hosted-cloud-ovhcloud) with these settings to match the provisioned infrastructure. 
+Before starting the OpenNebula deployment, gather all parameters required for the automation process. **Update the inventory values** in the [Hosted Cloud OVHcloud repository](https://github.com/OpenNebula/hosted-cloud-ovhcloud) with these settings to match the provisioned infrastructure.
 
-For further details on the automated deployment procedure, refer to the following section: [Configure and deploy the Hosted Cloud OVHcloud repository](#Initial_setup)
+For further details on the automated deployment procedure, refer to the following section: [Configure and deploy the Hosted Cloud OVHcloud repository](#initial_setup).
 
 Each server is equipped with two network adapters dedicated to public connectivity and two adapters for private connectivity. The two interfaces within each segment will be **bonded** using the **default LACP parameters for Scale and High Grade servers**.
 
 The **Public network bond** is exclusively for OpenNebula service management, including cluster deployment, administration via the Sunstone Web UI or OpenNebula CLI, and connectivity between the Front-end and Virtualization hosts.
 
 The **Private network bond** provides network to virtual servers, leveraging the OVHcloud vRack. This bond supports private networking, which is segmented using 802.1Q VLANs, and enables public IP addressing for virtual servers. To assign public addresses to virtual servers, a dedicated IP range must be purchased and routed via the vRack. This setup ensures cluster management traffic is isolated from virtual machine networking.
 
-![Network](images/opennebula_network.png)
+![Network](images/opennebula_network.png){.thumbnail}
 
 > [!warning]
 > This guide assumes the default bonding setup. If you change the network mode (e.g. OLA), please double check that your interface names and bonds are correct before running the playbooks.
 >
 > For more information about the link aggregation settings, please consult the following guide : [Improving Network Resilience on Bare Metal servers](/pages/bare_metal_cloud/dedicated_servers/lacp-resilience-scale-hg/).
 >
 
-#### Bare Metal network settings <a name="Bare_metal_network_settings"></a>
+#### Bare Metal network settings <a name="bare_metal_network_settings"></a>
 
-From your OVHcloud Control Panel, navigate to `Bare Metal Cloud`{.action}, then select `Dedicated servers`{.action}. Open both management pages for your dedicated servers, and collect the highlighted parameters :
+From your OVHcloud Control Panel, navigate to `Bare Metal Cloud`{.action} section, then select `Dedicated servers`{.action}. Open both management pages for your dedicated servers, and collect the highlighted parameters :
 
-![dedicated servers administration page](images/bare_metal_network.png)
+![dedicated servers administration page](images/bare_metal_network.png){.thumbnail}
 
 | Description                              | Variable Names                                           | Comment                                                |
 |------------------------------------------|----------------------------------------------------------|--------------------------------------------------------|
@@ -109,7 +109,7 @@ From your OVHcloud Control Panel, navigate to `Bare Metal Cloud`{.action}, then
 
 To collect the network adapter names, connect to your dedicated server and execute the `ip address` command :
 
-![dedicated servers ip address](images/bare_metal_ip_address.png)
+![dedicated servers ip address](images/bare_metal_ip_address.png){.thumbnail}
 
 | Description                              | Variable Names                                                | Comment                                                |
 |------------------------------------------|---------------------------------------------------------------|--------------------------------------------------------|
@@ -120,10 +120,11 @@ To collect the network adapter names, connect to your dedicated server and execu
 
 **Public IP addresses**
 
-The public IP block ordered in the previous steps allows to attach direct public connectivity to virtual servers. For a public IP range deployed on vRack, the first, penultimate, and last addresses in any given IP block are always reserved for the network address, network gateway, and network broadcast respectively. 
+The public IP block ordered in the previous steps allows to attach direct public connectivity to virtual servers. For a public IP range deployed on vRack, the first, penultimate, and last addresses in any given IP block are always reserved for the network address, network gateway, and network broadcast respectively.
 
-This means that the first usable address is the second address in the block, as shown below :
-```
+This means that the first usable address is the second address in the block, as shown below:
+
+```bash
 46.105.135.96   Reserved : Network address
 46.105.135.97   First usable IP
 46.105.135.98
@@ -152,7 +153,6 @@ Declare a bridge network for public IP addresses using all usable addresses of y
 | VMs Public NETWORK MASK                  | `vn.vm_public.template.NETWORK_MASK`                          | IP range netmask: 255.255.255.240 for example for a /28 network   |
 | VMs Public GATEWAY                       | `vn.vm_public.template.GATEWAY`                               | Penultimate IP address in the range, Network gateway: 46.105.135.110 in the example  |
 
-
 **Private IP addresses**
 
 On the private network bond, deploy one 802.1Q virtual network per private network. For each virtual network, create a section in the Ansible inventory file, and declare the VLAN ID, IP range and netmask.
@@ -164,91 +164,104 @@ On the private network bond, deploy one 802.1Q virtual network per private netwo
 | VMs Private IP Range, number of usable addresses                    | `vn.vm_vlan*.template.AR.SIZE`  | Number of usable addresses, for example 50 fo IP range 10.1.10.100-10.1.10.149   |
 | VMs Private NETWORK MASK                 | `vn.vm_vlan*.template.NETWORK_MASK`                           | IP range netmask: 255.255.255.0 for example for a /24 network   |
 
-### Step 3 - Configure and deploy the Hosted Cloud OVHcloud repository <a name="Initial_setup"></a>
+### Step 3 - Configure and deploy the Hosted Cloud OVHcloud repository <a name="initial_setup"></a>
 
 The deployment uses the **OpenNebula Hosted Cloud OVHcloud repository**.
 
 The high-level deployment steps are:
 
-1.  **Clone** the deployment repository,
-2.  **Install** the dependencies listed in the [Requirements section](https://github.com/OpenNebula/hosted-cloud-ovhcloud?tab=readme-ov-file#requirements),
-3.  **Update** the inventory parameters in the repository with the configuration gathered above,
-4.  **Launch deployment commands** :
-    * `make pre-tasks-ovhcloud` : Patch Ubuntu kernel and perform networking setup.
-    * `make deployment` : Deploy OpenNebula.
-    * `make validation` : Validate the automated deployment.
+1. **Clone** the deployment repository,
+2. **Install** the dependencies listed in the [Requirements section](https://github.com/OpenNebula/hosted-cloud-ovhcloud?tab=readme-ov-file#requirements),
+3. **Update** the inventory parameters in the repository with the configuration gathered above,
+4. **Launch deployment commands**:
+    - `make pre-tasks-ovhcloud`: Patch Ubuntu kernel and perform networking setup.
+    - `make deployment`: Deploy OpenNebula.
+    - `make validation`: Validate the automated deployment.
 
 ### Step 4 - Adding dedicated servers to an active OpenNebula infrastructure
 
 To extend the cloud with new servers:
 
-1.  **Provision** the new host as detailed in the [Setting up your OVHcloud infrastructure](#Infrastructure_Provisioning) section ;
-2.  **Collect** the necessary configuration parameters, especially the bare-metal network settings ;
-3.  **Re-execute** the deployment and verification commands from the [Configure and deploy the Hosted Cloud OVHcloud repository](#Initial_setup) section.
+1. **Provision** the new host as detailed in the [Setting up your OVHcloud infrastructure](#infrastructure_Provisioning) section.
+2. **Collect** the necessary configuration parameters, especially the bare-metal network settings.
+3. **Re-execute** the deployment and verification commands from the [Configure and deploy the Hosted Cloud OVHcloud repository](#initial_setup) section.
 
 ### Step 5 - Operate your cloud infrastructure
 
 The following section explains how to access a Hosted OpenNebula Cloud Deployment via the web UI, and instantiate and access a virtual machine.
 
-This guide provides the basic steps. If you need a more detailed guide, please refer to [OpenNebula public documentation](https://docs.opennebula.io/7.0/product/virtual_machines_operation/virtual_machines/)
+This guide provides the basic steps. If you need a more detailed guide, please refer to [OpenNebula public documentation](https://docs.opennebula.io/7.0/product/virtual_machines_operation/virtual_machines/).
 
 ### Create a template from OpenNebula Public marketplace
 
-From the OpenNebula Public marketplace, search and import virtual server templates needed for your infrastructure. The example below imports the Debian 13 "Trixie" template. 
+From the OpenNebula Public marketplace, search and import virtual server templates needed for your infrastructure. The example below imports the Debian 13 "Trixie" template:
+
+![user guide template 1](images/user_guide_template_1.png){.thumbnail}
 
-![user guide template 1](images/user_guide_template_1.png)
-![user guide template 2](images/user_guide_template_2.png)
+![user guide template 2](images/user_guide_template_2.png){.thumbnail}
 
 ### Start a new virtual server
 
 Based on the imported template, create a new virtual server instance.
 
-![user guide create vm 1](images/user_guide_create_vm_1.png)
-![user guide create vm 2](images/user_guide_create_vm_2.png)
-![user guide create vm 3](images/user_guide_create_vm_3.png)
+![user guide create vm 1](images/user_guide_create_vm_1.png){.thumbnail}
+
+![user guide create vm 2](images/user_guide_create_vm_2.png){.thumbnail}
+
+![user guide create vm 3](images/user_guide_create_vm_3.png){.thumbnail}
 
 You can adjust disk storage capacity, CPU and RAM allocation during this setup phase.
 
-![user guide create vm 4](images/user_guide_create_vm_4.png)
-![user guide create vm 5](images/user_guide_create_vm_5.png)
-![user guide create vm 6](images/user_guide_create_vm_6.png)
+![user guide create vm 4](images/user_guide_create_vm_4.png){.thumbnail}
+
+![user guide create vm 5](images/user_guide_create_vm_5.png){.thumbnail}
+
+![user guide create vm 6](images/user_guide_create_vm_6.png){.thumbnail}
 
-Finally, attach network adapters. In this example, we provide a public IP to this server, based on the public IP range we created during the OpenNebula automated deployment. Without any override, an available IP address form the public range will be picked for this interface.
+Finally, attach network adapters. In this example, we provide a public IP to this server, based on the public IP range we created during the OpenNebula automated deployment. Without any override, an available IP address from the public range will be picked for this interface.
 
-![user guide create vm 7](images/user_guide_create_vm_7.png)
-![user guide create vm 8](images/user_guide_create_vm_8.png)
+![user guide create vm 7](images/user_guide_create_vm_7.png){.thumbnail}
+
+![user guide create vm 8](images/user_guide_create_vm_8.png){.thumbnail}
 
 ### Check connectivity
 
-You can use the virtual server console to check the deployment and the server connectivity. Setup the root password using virtual machine context variables.
+You can use the virtual server console to check the deployment and the server connectivity. Set up the root password using virtual machine context variables.
+
+![user guide check vm 1](images/user_guide_connectivity_1.png){.thumbnail}
 
-![user guide check vm 1](images/user_guide_connectivity_1.png)
-![user guide check vm 2](images/user_guide_connectivity_2.png)
+![user guide check vm 2](images/user_guide_connectivity_2.png){.thumbnail}
 
 Run your virtual server console to validate the deployment.
 
-![user guide check vm 3](images/user_guide_connectivity_3.png)
-![user guide check vm 4](images/user_guide_connectivity_4.png)
+![user guide check vm 3](images/user_guide_connectivity_3.png){.thumbnail}
+
+![user guide check vm 4](images/user_guide_connectivity_4.png){.thumbnail}
 
 ### Update virtual servers settings
 
 Use virtual server settings to update the server configuration. This example shows the hot-plugging of a private network adapter to the virtual server.
 
-![user guide hotplug 1](images/user_guide_hotplug_1.png)
-![user guide hotplug 2](images/user_guide_hotplug_2.png)
-![user guide hotplug 3](images/user_guide_hotplug_3.png)
-![user guide hotplug 4](images/user_guide_hotplug_4.png)
+![user guide hotplug 1](images/user_guide_hotplug_1.png){.thumbnail}
+
+![user guide hotplug 2](images/user_guide_hotplug_2.png){.thumbnail}
+
+![user guide hotplug 3](images/user_guide_hotplug_3.png){.thumbnail}
+
+![user guide hotplug 4](images/user_guide_hotplug_4.png){.thumbnail}
 
 ### Destroy virtual server
 
-Finally, as a cleanup step, terminate the virtual server by clicking the red “Trash can” icon.
+Finally, as a cleanup step, terminate the virtual server by clicking the red "Trash can" icon.
 
-![user guide terminate 1](images/user_guide_terminate_1.png)
-![user guide terminate 2](images/user_guide_terminate_2.png)
+![user guide terminate 1](images/user_guide_terminate_1.png){.thumbnail}
+
+![user guide terminate 2](images/user_guide_terminate_2.png){.thumbnail}
 
 ## Go further
 
-**External resources :**
+**External resources:**
+
 - If you need more information about OpenNebula, you may consult the [OpenNebula Website](https://opennebula.io/) or the [official OpenNebula documentation](https://docs.opennebula.io/).
 - If you need more information about Ansible, you may consult the [Ansible page on the RedHat website](https://www.redhat.com/en/ansible-collaborative?) or the [official Ansible documentation](https://docs.ansible.com/).
 - The OpenNebula deployment repository used and referenced in this guide is [Hosted Cloud OVHcloud](https://github.com/OpenNebula/hosted-cloud-ovhcloud).