Configuring vRack for Public Cloud
9680 Ansichten
23.12.2025 
Cloud / Network Gateway for Public Cloud
Objective
The OVHcloud vRack is a private network solution that enables our customers to route traffic between OVHcloud dedicated servers as well as other OVHcloud services. At the same time, it allows you to add Public Cloud instances to your private network to create an infrastructure of physical and virtual resources.
This guide explains how to configure Public Cloud instances within your vRack.
Requirements
- A Public Cloud project in your OVHcloud account
- Access to the OVHcloud Control Panel
- An OpenStack user (optional)
- Basic networking knowledge
Interfaces
Creating a vRack or adding an instance into the network can be done using the OVHcloud Control Panel, the OVHcloud APIv6, the OpenStack API, the Horizon interface or Terraform.
Depending on your technical profile and needs, it is mostly up to you which interface or method to use. For each option, the guide instructions below describe the necessary steps.
To begin with, the following provides a brief description of the possible actions according to the chosen method/interface.
OVHcloud Control Panel
The OVHcloud Control Panel is a fully visual interface, ideally suited for managing multiple VLANs. You will also have the possibility to customise the private IP range, which by default is in 10.1.0.0/16.
The VLAN will be deployed to the selected Region. You will also have the option of activating the gateways or not, enabling DHCP distributions, etc.
You can also manage billing for your services in the OVHcloud Control Panel.
Horizon
The Horizon interface (independent from OVHcloud) is the original implementation of the OpenStack dashboard, which provides a web user interface to OpenStack services, including Nova, Swift, Keystone, etc.
This multifunctional, technical interface allows you to manage almost all OpenStack actions. It is one of the necessary interfaces if you need to manage more than two VLANS, add private network interfaces to your instances, manage custom images, etc.
Please refer to this guide to familiarise yourself with Horizon.
Horizon functions zone-specific, therefore you need to remember to choose your logical (geographic) work zone at the top left of your interface (GRA5, SBG3, BHS1, etc.).
OVHcloud APIv6
Every action you take in your OVHcloud Control Panel can be called with the OVHcloud APIv6. It even offers more possibilities than the graphical interface.
The API interface is less visual than the OVHcloud Control Panel but will allow you to perform a large number of actions. You can manage and customise your VLAN, add interfaces to your instances, or create highly customised servers.
You can simply access it from our web page but also use it to create your PHP or Python scripts.
This way, you can freely automate basic tasks with scripts, optimise your own functions and much more.
You may need to retrieve various information before using some API calls because a specific input is required.
Please refer to this guide to get started with the OVHcloud APIv6.
OpenStack API
Public Cloud services can be administrated using Linux or Windows command lines after downloading and installing OpenStack tools.
This method requires a good knowledge of Linux or Windows to take advantage of it, but it allows you to leverage all the power of OpenStack.
Depending on the layer you want to manage, you will need to use the Nova (compute), Neutron (network), Glance (image) or Swift (Object Storage) client. The latest addition to this assortment, the OpenStack client, makes it possible to manage almost all OpenStack layers directly.
With the OpenStack API, you can also easily automate this management through your scripts.
To know more about the usage of the OpenStack API, please consult these guides:
You will then be able to use the APIs dedicated to OpenStack as needed:
- Nova (compute)
- Glance (image)
- Cinder (image)
- Neutron (network)
In some cases, it will be easier to use the OpenStack APIs and in others, Nova, Neutron, etc.
Moreover, some features may be missing from the OpenStack API depending on the version of your client and operating system. For the purpose of making this guide more accessible, it presents the simplest and most intuitive options. You may consult the official OpenStack documentation if you wish to go further in learning about its use.
OpenStack CLI
You can manage your OVHcloud Public Cloud services and vRacks directly from your Linux or Windows terminal using the OpenStack CLI.
This interface allows you to manage all OpenStack layers:
- Nova: instances (compute)
- Neutron: networks
- Glance: images
- Cinder: volumes
The CLI centralizes these features and can be integrated into your scripts to automate your tasks.
Before you begin, please consult the following guides:
The OpenStack CLI is useful for managing your vRack, but some functions may vary depending on the version of the client or operating system. Please refer to the official OpenStack documentation.
Terraform
Terraform can also be used to manage OVHcloud infrastructures.
For that you need to cherry-pick the correct terraform provider & resource. Find more information in our guide on using Terraform with OVHcloud.
Instructions
Step 1: Activating and managing a vRack
The vRack is managed at the OVHcloud infrastructure level, which means that you can only administer it in your OVHcloud Control Panel and the OVHcloud APIv6.
This does not apply to newly created projects which are now automatically delivered with a vRack. To view the vRack once the project has been created, go the Network section and click on vRack private network to view the vRack(s).
If you have an older project and don't have a vRack, you need to order one. Using the vRack itself is free of charge and it can be delivered within a few minutes.
In the left-hand menu, click the button Add a service (shopping cart icon). Use the filter at the top of the page or scroll down to find the service vRack.
You will be redirected to another page to validate the order, it will take a few minutes for the vRack to be setup in your account.
Once the service is active, you will find it in your Control Panel in the Network section > vRack private network, labelled "pn-xxxxxx".
Click on your vRack, then select the project you want to add to the vRack from the list of eligible services and click the Add button.
To continue configuring your vRack from the OVHcloud Control Panel, continue reading this guide from Step 2: Create a private network in the vRack, under the From the OVHcloud Control Panel tab.
Step 1: Activating and managing a vRack
Log in to the OVHcloud APIv6 interface according to the relevant guide (First steps with the OVHcloud API) and follow these steps:
Creating the cart
This call will create an ID for your 'shopping cart'. You can add as many articles as you want before you validate it.
In this case, the order of a vRack alone is free. Remember your cart number (cartId), it will be required for the rest.
Retrieving the necessary information for the vRack order
This call will allow you to retrieve all the information needed to order the vRack. Copy the following:
cartId, duration, planCode, and pricingMode.
Adding the vRack to the cart
This call allows you to add the vRack to the cart by adding all the necessary information to the order.
For a vRack, this would be, for example:
cartId: [your cart identifier]
duration: "P1M"
planCode: "vrack"
pricingMode: "default"
quantity: 1
Once you have validated the order, you will receive an item number ("itemId"). Keep this information, it will be useful if you wish to make changes before the validation of the cart.
Validating the cart
Once you have put all the items in your cart, you will need to validate it:
This call will validate the cart and create a purchase order ("orderId"). Keep this information, it will be necessary to validate the order.
Validating the final order
To validate the order, you have two possibilities:
-
Pass through the visible URL when the cart is validated. URL example: https://www.ovh.com/cgi-bin/order/displayOrder.cgi?orderId=12345678&orderPassword=xxxxxxxxxx
-
Validate using this call:
Even if it is a €0 purchase order, it is necessary to simulate a purchase order payment (orderId). Your order form will then be validated and processing will begin.
Once the free order has been validated, it may take a few minutes for the vRack to be activated.
Step 2: Adding your Public Cloud project to the vRack
Once the vRack is active, you will need to integrate your Public Cloud project(s) into the vRack.
Log in to the OVHcloud APIv6 interface according to the relevant guide: First steps with the OVHcloud API.
In case the project ID is unknown, the calls below allow you to retrieve it.
Identifying the project
This call retrieves the list of projects.
This call identifies the project via the "description" field.
Adding the project to the vRack
Once the project ID and the vRack name are known, their association is made through the following call:
Fill in the fields with the information previously retrieved:
- serviceName: vRack name in the form "pn-xxxxxx".
- project: The Public Cloud project ID in the form of a 32-character string.
This call initializes the association of the project and the vRack. The task ID must then be retrieved to check the progress.
Checking the progress of the task
You can view the progress of the task with this call:
This call is optional and only allows you to check the status of the task. Once it is complete, you can proceed to the next step.
Step 2: Creating a private network in the vRack
It is necessary to create a private network with a virtual local area network (VLAN) so that the connected instances can communicate with each other.
With the Public Cloud service, you can create up to 4 000 VLANs within one vRack. This means that you can use each private IP address up to 4 000 times. Thus, for example, 192.168.0.10 of VLAN 2 is different from IP 192.168.0.10 of VLAN 42.
This can be useful in order to segment your vRack between multiple virtual networks.
From the OVHcloud Control Panel and OVHcloud APIv6, you can customise all settings: deployment mode and region, VLAN name and ID, private IP address range (e.g. 10.0.0.0/16), DHCP, and gateway.
On dedicated servers, you are using VLAN 0 by default. The OpenStack infrastructure requires to specify your VLAN ID directly at the infrastructure level.
Unlike dedicated servers, there is no need to tag a VLAN directly on a Public Cloud instance.
To learn more about this topic, please refer to the guide "Creating multiple vLANs in a vRack".
vRack is managed at the OVHcloud infrastructure level, meaning you can only administrate it in the OVHcloud Control Panel and the OVHcloud APIv6.
Because OpenStack is not located at the same level, you will not be able to customise VLANs through the Horizon interface or OpenStack APIs.
Once you have your vRack set, the next step is to create a private network.
In the Public Cloud tab, click on Private Network in the left-hand menu under Network.
Click on the button Add Private Network. The following page allows you to customise multiple settings.
To begin, select a deployment mode and the region in which you want to create the private network.
In the next step, a number of options are presented to you:
In the Private Network Name field, set a name for your private network.
Layer 2 network option
If you tick the Set VLAN ID box, you will be able to manually choose a VLAN ID number between 0 and 4 000.
If you do not tick the box, the system will assign a random VLAN ID number to your private network.
If you want to be able to communicate with dedicated servers in this VLAN, please consult the guide: Creating multiple vLANs in a vRack.
DHCP address distribution options
The default DHCP range is 10.1.0.0/16. You can use a different private range of your choice, or disable DHCP for this private network.
Network Gateway Options
- Announce the first address of a given CIDR. as the default gateway (DHCP option 3): When this option is enabled, the DHCP server advertises the first address in the CIDR as the default gateway to machines connected to the network.
- Assign a Gateway and connect to the private network:Select this option if you intend to create instances with a private network only. For more information, please consult the following guides: Creating a private network with Gateway and Creating and connecting to your first Public Cloud instance.
If the second option is greyed out, it means the region selected does not support it. For more information, please refer to our regions availability page.
Once done, click on Configure your private network to start the process.
Creating the private network may take several minutes.
Once logged in to the OVHcloud APIv6 interface, follow these steps:
Step 1: Retrieving the required information
Public Cloud project
This call retrieves the list of projects.
This call identifies the project via the "description" field.
vRack
In the field "serviceName", specify the ID of your project. Save the vRack ID information in the form "pn-xxxxx".
Step 2: Creating the private network
Fill in the fields with the information previously obtained:
- serviceName: project ID.
- name: name of your VLAN.
You can leave the "Region" field blank in order to enable it for all regions.
The VLAN identifier (vlanId) is required if you want to create a specific VLAN.
The creation will take a few moments.
You can check your VLAN information with the following call:
This call retrieves the "networkId" in this form: name-vrack_vlanId.
For example, VLAN 42: pn-xxxxxx_42.
Step 3: Creating a subnet
By default, if you do not add a subnet, the IP range used is:
10.1.0.0/16If you want to manage IP assignments yourself, you will need to create a subnet.
To do this, once the VLAN is created, you will need to create the subnet for each affected area by the following call:
Fill in the fields according the following table.
| Field | Description |
|---|---|
| serviceName | ID of the project. |
| networkId | Your network ID, retrieved with previous steps. Example: pn-xxxxxx_42 for VLAN 42. |
| dhcp | Check box for enabling / uncheck for disabling DHCP in the VLAN. |
| end | Last address of the subnet in this region. Example: 192.168.1.50. |
| network | Subnet IP block. Example: 192.168.1.0/24. |
| region | Example: SBG3. |
| start | First address of the subnet in this region. Example: 192.168.1.15. |
This is the stage of creating the subnet by region. You can enable or disable private IP address assignment dynamically through DHCP.
You will need to do the same for each region where your instances are present.
Be careful to separate your IP address pools for different regions. For example:
- From 192.168.0.2 to 192.168.0.254 for SBG1.
- From 192.168.1.2 to 192.168.1.254 for GRA1.
In Terraform, you will need to use the OpenStack provider. You can download an example of a complete terraform script in this GitHub repository.
The OVHcloud specific part for vRack integration is the value_specs parameter.
In the following example we specify the VLAN_ID to which we want the network to be part of through --provider-network-type and --provider-segment.
You can remove those parameters. In that case, an available VLAN_ID will be used.
Step 3: Integrating an instance into vRack
There are two possible scenarios:
- The instance to be integrated does not exist yet.
- An existing instance needs to be added to the vRack.
In case of a new instance
If you need assistance, follow this guide first: Creating an instance in the OVHcloud Control Panel. When creating an instance, you can choose, in Step 5, a network mode, followed by a private network to integrate your instance into.
You will be able to connect your instance to only one vRack from the OVHcloud Control Panel.
To add multiple interfaces, you will need to go through the OpenStack or Horizon APIs.
Once logged in to the OVHcloud APIv6 interface, follow these steps:
Step 1: Retrieving the required information
Retrieving the project ID
Retrieving the networkID of the public network (Ext-Net)
Retrieving the networkID of the private network (vRack interface previously created)
The identifier will have the form: "pn-xxxxx_yy" in which yy is the VLAN number.
Retrieving the ID of the chosen instance type (flavorId)
You can limit the list by specifying the creation region of your instance.
Retrieving the ID of the chosen image (imageId)
You can limit the list by specifying the creation region of your instance.
Retrieving your OpenStack SSH key ID (sshKeyId)
If you have not added an SSH key to your OVHcloud Control Panel yet, you can do so using the following call:
*Deploying the instance
Once all the elements necessary for the deployment are gathered, you can use the following call:
You will need to fill in at least the following fields:
| Field | Description |
|---|---|
| serviceName | ID of the Public Cloud project. |
| flavorId | ID of the instance type (example: D2-2, B2-7, WIN-R2-15, etc.). |
| imageId | ID of the image for the deployment (example: Debian 9, Centos 7, etc.). |
| name | Name for your instance. |
| networks | In the "networkId" section, indicate the public network identifier (Ext-Net) or your VLAN (pn-xxxxxx_yy). You can click the "+" button to add more networks. |
| region | Region for your instance deployment (example: GRA5). |
| sshKeyId | ID of your OpenStack SSH key. |
Once the call is complete, if all information is correctly filled in, the instance will be created with one or more network interfaces.
Depending on operating systems, you will need to manually configure your private network interfaces to be considered.
Because OpenStack is unable to prioritise the public interface of the vRack interface, the vRack interface may sometimes pass as the default route.
The direct consequence is that the instance is unreachable from a public IP.
One or more reboots of the instance from the Control Panel can resolve this situation.
The other solution is to connect to the instance via another server in the same private network. You can also correct the network configuration of the instance through Rescue mode.
The following steps are necessary to create an instance directly in the vRack.
Retrieving the required information
Public and private networks:
or
You will need to note the network IDs of interest:
- Ext-Net for a public IP address.
- The VLAN(s) required for your configuration.
Also note the information detailed in the Nova API user guide:
- ID or name of the OpenStack SSH key.
- ID of the instance type (flavor).
- ID of the desired image (operating system, snapshot, etc.).
Deploying the instance
With the previously retrieved items, an instance can be created, including it directly in the vRack:
Example:
or
Example:
You can set the IP address of the instance of your vRack interface at the OpenStack level.
To do this, you can add a single argument to the function "--nic":
--nic net-id=[ID-Network],v4-fixed-ip=[IP_static_vRack]
Example:
--nic net-id=[ID-vRack],v4-fixed-ip=192.168.0.42
Verifying the instance
After a few moments you can check the list of existing instances to find the server you created:
In case of an existing instance
The OVHcloud Control Panel allows you to attach an instance to one or more private networks but does not offer advanced network interface configuration. If you want to customise further, you will need to manage them either through the OVHcloud APIv6, through the OpenStack APIs or via Horizon.
The required action is simply to add a new network interface to your server, in addition to the existing one.
For example, if you have a public interface eth0, you will add the interface eth1.
The configuration of this new interface is rarely automatic. You will therefore need to set a static IP or configure DHCP, depending on your infrastructure.
Log in to the OVHcloud Control Panel, go to the Public Cloud section and select the Public Cloud project concerned.
Click on Instances in the left-hand navigation bar and then on ⁝ to the right of the instance. Select Instance details.
This will open the instance dashboard. Click on the ⁝ button in the box "Networks", next to "Private networks", and select Attach a network.
In the popup window that appears, select the private network(s) to attach to your instance and click Confirm.
If you need to integrate an existing instance into the vRack, it is not possible to do so from your OVHcloud Control Panel. You will need to use Horizon, the OpenStack API or the OVHcloud APIv6.
The required action is simply to add a new network interface to your server, in addition to the existing one.
For example, if you have a public interface eth0, you will add the interface eth1.
The configuration of this new interface is rarely automatic. You will therefore need to set a static IP or configure DHCP, depending on your infrastructure.
The steps below describe how to manage the network interfaces of your instances.
Step 1: Retrieving the required information
Retrieving the project ID
Retrieving the instance ID
Retrieving the networkID of the public network (Ext-Net)
Retrieving the networkID of the private network (vRack interface previously created)
The identifier will have the form: "pn-xxxxx_yy" in which yy is the VLAN number.
Step 2: Adding an interface to your instance
Once all the elements necessary are gathered, you can use the following call:
You will need to fill in at least the following fields:
| Field | Description |
|---|---|
| serviceName | ID of the Public Cloud project. |
| instanceId | ID of the instance. |
| networkId | Enter the public network identifier (Ext-Net) or your VLAN (pn-xxxxxx_yy). |
| ip | Define a specific IP (only works for private interfaces). |
Once the call is complete, if all information is correctly filled in, a new interface will be added to your instance.
Your OVHcloud instance will have a new network interface in addition to the public interface (Ext-Net).
In the instance summary, you can see the private IP address that is automatically assigned to your interface.
It is your responsibility to correctly configure the interface through DHCP or by using the proper IP addresses through a static IP configuration.
Step 3: Removing an interface from your instance
Detaching a network interface is permanent.
However, it is important to note that if you detach the "Ext-Net" interface (public IP), this address will be released and put back into circulation. It is not possible to just reassign it.
This action is only required if you wish to isolate your server in the vRack (private network), or if you wish to remove it from one or more VLANs.
Once all the necessary information is retrieved, you can use the following call to remove an interface:
You will need to fill in at least the following fields:
| Field | Description |
|---|---|
| serviceName | ID of the Public Cloud project. |
| instanceId | ID of the instance. |
| networkId | Enter the public network identifier (Ext-Net) or your VLAN (pn-xxxxxx_yy). |
Log in to the Horizon interface as mentioned above.
Choose the proper work zone.
Select Compute and then Instances from the menu.
Adding a private interface
To add an interface, click on the arrow in the Actions column to access the possible actions on the instance. Select Attach Interface.
Select your interface and confirm.
Your OVHcloud instance will have a new network interface in addition to the public interface (Ext-Net).
In the instance summary, you can see the private IP address that is automatically assigned to your interface.
It is your responsibility to correctly configure the interface through DHCP or by using the proper IP addresses through a static IP configuration.
Detaching a network private interface
Detaching a network interface is permanent.
However, it is important to note that if you detach the "Ext-Net" interface (public IP), this address will be released and put back into circulation. It is not possible to just reassign it.
This action is only required if you wish to isolate your server in the vRack (private network), or if you wish to remove it from one or more VLANs.
To detach a private interface, click on the arrow in the Actions column to access the possible actions on the instance. Select Detach Interface.
Select your interface and confirm.
The following steps are necessary to integrate an existing instance into the vRack.
Retrieving the required information
Identify your instances:
or
Public and private networks:
or
You will need to note the network IDs of interest:
- Ext-Net for a public IP address
- The VLAN(s) required for your configuration
Adding a private network interface
In order to attach a new interface, execute the following command:
Example:
You can verify that the action has been performed:
or
Removing a network interface
Detaching a network interface is permanent.
However, it is important to note that if you detach the "Ext-Net" interface (public IP), this address will be released and put back into circulation. It is not possible to just reassign it.
This action is only required if you wish to isolate your server in the vRack (private network), or if you wish to remove it from one or more VLANs.
In order to detach an interface, you will first need to identify the Neutron port that has been created. You can do this by using the following commands:
or
Once you have identified the port to remove, you can execute the following command:
Example:
Go further
Creating multiple vLANs in a vRack
If you need training or technical assistance to implement our solutions, contact your sales representative or click on this link to get a quote and ask our Professional Services experts for assisting you on your specific use case of your project.
Join our community of users.
Creating a private network with Gateway (EN)
1294