You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: pages/bare_metal_cloud/dedicated_servers/opennebula-deployment/guide.en-gb.md
+61-18Lines changed: 61 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,17 +6,17 @@ updated: 2025-11-18
6
6
7
7
## Introduction
8
8
9
-
OpenNebula is a powerful, open-source cloud management platform (CMP) designed to manage and provision virtualized infrastructure.
9
+
OpenNebula is a powerful, open-source **Cloud Management Platform** (CMP) designed to manage and provision virtualized infrastructure.
10
10
11
-
It acts as an orchestrator, turning physical infrastructure into a managed IaaS (Infrastructure as a Service) cloud that is accessible via a unified control interface. It supports major hypervisors and allows for hybrid deployments by integrating with public cloud providers, such as OVHcloud.
11
+
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.
12
12
13
-
OpenNebula supports the deployment of its solution on OVHcloud infrastructure, which results in a cloud environment that is validated as part of the **OpenNebula Cloud-Ready Certification Program**.
13
+
The deployment of OpenNebula on OVHcloud infrastructure is validated as part of the **OpenNebula Cloud-Ready Certification Program**.
14
14
15
-
To streamline this process, OpenNebula provides [a set of **Ansible playbooks** called Hosted Cloud OVHcloud](https://github.com/OpenNebula/hosted-cloud-ovhcloud) for automated deployment and verification,**which you will need to use**in this guide.
15
+
To streamline this process, OpenNebula provides a set of **Ansible playbooks** called [Hosted Cloud OVHcloud](https://github.com/OpenNebula/hosted-cloud-ovhcloud) for automated deployment and verification.**You will use these playbooks**throughout this guide.
16
16
17
17
## Objective
18
18
19
-
This guide details the complete path to creating an OpenNebula Hosted Cloud on OVHcloud, including the custom architecture and hardware specifications.
19
+
This guide details the complete process of creating an OpenNebula Hosted Cloud on OVHcloud, including the custom architecture and hardware specifications.
20
20
21
21
Following this guide, you will be able to:
22
22
@@ -29,31 +29,72 @@ Following this guide, you will be able to:
29
29
30
30
-**Two**[dedicated servers](/links/bare-metal/bare-metal) from the Scale or High Grade ranges,
31
31
- An active [vRack](/links/network/vrack) service,
32
-
- A public block of Additional IP addresses, sized according to your needs,
32
+
- A public block of [Additional IP](/links/network/additional-ip) addresses, sized according to your needs,
33
33
- Access to the [OVHcloud Control Panel](/links/manager).
34
34
35
+
> [!Primary]
36
+
>
37
+
> The reference OpenNebula deployment uses the following configuration:
> Servers from the [Scale range](/links/bare-metal/scale) are suitable for small to medium cloud environments.
56
+
>
57
+
> Servers from the [High Grade range](/links/bare-metal/hg) are more appropriate for heavier production workloads.
58
+
>
59
+
> For more information about scaling, please consult the [OpenNebula guide for Scalability Testing and Tuning](https://docs.opennebula.io/7.0/product/control_plane_configuration/large-scale_deployment/scalability/).
60
+
35
61
## Instructions
36
62
37
-
### Setting up your infrastructure <aname="Infrastructure_Provisioning"></a>
63
+
### Step 1 - Setting up your OVHcloud infrastructure <aname="Infrastructure_Provisioning"></a>
38
64
39
65
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).
40
66
41
67
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).
42
68
43
-
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.
69
+
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.
70
+
71
+
> [!warning]
72
+
>
73
+
> **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.
74
+
>
75
+
> 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/).
76
+
>
77
+
78
+
### Step 2 - Collecting the Bare Metal & Network settings
44
79
45
-
### Collecting the infrastructure configuration
80
+
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.
46
81
47
-
To begin with the OpenNebula deployment, extract the required parameters that the deployment automation relies upon. **Update the inventory values** for the [Hosted Cloud OVHcloud repository](https://github.com/OpenNebula/hosted-cloud-ovhcloud) using all collected settings to match the provisioned infrastructure. For further details on the automated deployment procedure, refer to the following section: [Initial setup](#Initial_setup)
82
+
For further details on the automated deployment procedure, refer to the following section: [Configure and deploy the Hosted Cloud OVHcloud repository](#Initial_setup)
48
83
49
-
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 [OVHcloud Link Aggregation](https://www.ovhcloud.com/en/bare-metal/ovhcloud-link-aggregation/) service.
84
+
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**.
50
85
51
86
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.
52
87
53
88
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.
54
89
55
90
56
91
92
+
> [!warning]
93
+
> 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.
94
+
>
95
+
> 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/).
96
+
>
97
+
57
98
#### Bare Metal network settings <aname="Bare_metal_network_settings"></a>
58
99
59
100
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 :
@@ -75,11 +116,13 @@ To collect the network adapter names, connect to your dedicated server and execu
75
116
| Frontend/KVM Host public NICs name |`public_nics.name`| public_aggregation network adapter names |
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 :
123
+
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.
124
+
125
+
This means that the first usable address is the second address in the block, as shown below :
83
126
```
84
127
46.105.135.96 Reserved : Network address
85
128
46.105.135.97 First usable IP
@@ -121,7 +164,7 @@ On the private network bond, deploy one 802.1Q virtual network per private netwo
121
164
| 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 |
122
165
| VMs Private NETWORK MASK |`vn.vm_vlan*.template.NETWORK_MASK`| IP range netmask: 255.255.255.0 for example for a /24 network |
123
166
124
-
### Initial setup <aname="Initial_setup"></a>
167
+
### Step 3 - Configure and deploy the Hosted Cloud OVHcloud repository <aname="Initial_setup"></a>
125
168
126
169
The deployment uses the **OpenNebula Hosted Cloud OVHcloud repository**.
127
170
@@ -135,15 +178,15 @@ The high-level deployment steps are:
135
178
*`make deployment` : Deploy OpenNebula.
136
179
*`make validation` : Validate the automated deployment.
137
180
138
-
### Adding dedicated servers to an active infrastructure
181
+
### Step 4 - Adding dedicated servers to an active OpenNebula infrastructure
139
182
140
183
To extend the cloud with new servers:
141
184
142
-
1.**Provision** the new host as detailed in the [Setting up your infrastructure](#Infrastructure_Provisioning) section ;
185
+
1.**Provision** the new host as detailed in the [Setting up your OVHcloud infrastructure](#Infrastructure_Provisioning) section ;
143
186
2.**Collect** the necessary configuration parameters, especially the bare-metal network settings ;
144
-
3.**Re-execute** the deployment and verification commands from the [Initial setup](#Initial_setup) section.
187
+
3.**Re-execute** the deployment and verification commands from the [Configure and deploy the Hosted Cloud OVHcloud repository](#Initial_setup) section.
145
188
146
-
##User guide
189
+
### Step 5 - Operate your cloud infrastructure
147
190
148
191
The following section explains how to access a Hosted OpenNebula Cloud Deployment via the web UI, and instantiate and access a virtual machine.
0 commit comments