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
+14-14Lines changed: 14 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,26 +10,26 @@ OpenNebula is a powerful, open-source cloud management platform (CMP) designed t
10
10
11
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.
12
12
13
-
OpenNebula supports the deployment of their solution on OVHcloud infrastructure, which results in a cloud environment that is validated as part of the **OpenNebula Cloud-Ready Certification Program**.
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**.
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.
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.
16
16
17
17
## Objective
18
18
19
19
This guide details the complete path to 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
23
-
- Request necessary resources using your OVHcloud account.
24
-
- Prepare the Ansible deployment project with all required configuration.
25
-
- Perform OpenNebula deployment over these resources.
23
+
- Request necessary resources using your OVHcloud account,
24
+
- Prepare the Ansible deployment project with all required configuration,
25
+
- Perform OpenNebula deployment over these resources,
26
26
- Check the operation with an automated verification procedure.
27
27
28
28
## Requirements
29
29
30
-
-**Two**[dedicated servers](/links/bare-metal/bare-metal) from the Scale or High Grade ranges ;
31
-
- An active [vRack](/links/network/vrack) service ;
32
-
- A public block of Additional IP addresses, sized according to your needs ;
30
+
-**Two**[dedicated servers](/links/bare-metal/bare-metal) from the Scale or High Grade ranges,
31
+
- An active [vRack](/links/network/vrack) service,
32
+
- A public block of Additional IP addresses, sized according to your needs,
33
33
- Access to the [OVHcloud Control Panel](/links/manager).
34
34
35
35
## Instructions
@@ -44,7 +44,7 @@ Finally, from the OVHcloud Control Panel, open the `Network`{.action} section, t
44
44
45
45
### Collecting the infrastructure configuration
46
46
47
-
To proceed with 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)
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)
48
48
49
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.
50
50
@@ -79,7 +79,7 @@ To collect the network adapter names, connect to your dedicated server and execu
79
79
80
80
**Public IP addresses**
81
81
82
-
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 useable address is the second address in the block, as shown below :
82
+
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 :
83
83
```
84
84
46.105.135.96 Reserved : Network address
85
85
46.105.135.97 First usable IP
@@ -112,7 +112,7 @@ Declare a bridge network for public IP addresses using all usable addresses of y
112
112
113
113
**Private IP addresses**
114
114
115
-
On 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.
115
+
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.
@@ -127,9 +127,9 @@ The deployment uses the **OpenNebula Hosted Cloud OVHcloud repository**.
127
127
128
128
The high-level deployment steps are:
129
129
130
-
1.**Clone** the deployment repository ;
131
-
2.**Install** the dependencies listed in the [Requirements section](https://github.com/OpenNebula/hosted-cloud-ovhcloud?tab=readme-ov-file#requirements) ;
132
-
3.**Update** the inventory parameters in the repository with the configuration gathered above ;
130
+
1.**Clone** the deployment repository,
131
+
2.**Install** the dependencies listed in the [Requirements section](https://github.com/OpenNebula/hosted-cloud-ovhcloud?tab=readme-ov-file#requirements),
132
+
3.**Update** the inventory parameters in the repository with the configuration gathered above,
133
133
4.**Launch deployment commands** :
134
134
*`make pre-tasks-ovhcloud` : Patch Ubuntu kernel and perform networking setup.
0 commit comments