A flexible, private connection between your instances
The emergence of software-defined networks (SDNs) in cloud infrastructures has given users increased flexibility when it comes to network management. In this spirit, the OVHcloud Public Cloud lets you design and build your network architecture on demand. By creating private networks, you implement virtual switches that can hot-connect your project instances in real time, without any service interruptions.
Extended networks between regions
Public Cloud Private Networks are built on OVHcloud vRack technology. You can use it to extend private networks between OVHcloud data centers, connecting instances across different regions around the world through private communication channels.
You can create up to 4,000 level 2 private networks. In concrete terms, launching a Private Network implements a new VLAN, whose communications are only accessible to the resources connected to it. This isolation can be used to segment control plane and data plane networks, for example.
Extension to other OVHcloud services
You can also use the vRack to connect different OVHcloud services to one another. You can extend your Public Cloud Private Network to connect with your Private Cloud or dedicated servers, for example. This way, you can distribute your application to suit your needs, while keeping the connections private.
Create a Private Network
openstack network create net01
Create a subnet with DHCP
openstack subnet create subnet01 --network net01 --subnet-range 10.0.0.0/8
When you create a network, you can choose to use addressing via DHCP. If you choose this option, a DHCP server will be launched on the network to serve your settings.
The DHCP configuration can include the definition of the DNS servers that should serve your network. This way, you can point to the DNS server of your choice.
DHCP servers can serve a specific CIDR configuration, targeting only a part of the IP address range you have chosen.
Fixed or dynamic addresses
You can choose specific addresses in the network range for a port or instance. You will always need to configure this via DHCP, but you will retain control over the addressing plan by doing so.
Private networks' ports are independent of their instances, so you can detach a port from an instance without losing it. This can be useful for projects that involve infrastructure orchestration.
How many private networks can I create?
The technical limit is 4,000 private networks, but you may find that there is a quota limit for your project. You can request a quota increase via the OVHcloud Control Panel.
Can I manage addressing manually, or any way other than DHCP?
If you want to manage addressing differently, you can do this as you would with any other layer 2 network.
Can I connect my Public Cloud instances to the same private network as my dedicated server or Hosted Private Cloud?
Yes, all OVHcloud private networks are managed by our vRack technology. This means you can extend private networks between different services. Simply attach the same vRack to each of the solutions.
Can I connect two instances located on each side of the Atlantic via a Private Network, or any other location?
Yes. Once your project is connected to a vRack, all active locations can communicate with each other. Simply use the same VLAN number when creating private networks in each region.
What is the average latency between datacentres via a Private Network?
As an indication, here are some average measures. These values may change over time:
- Europe - Europe
- Strasbourg - Gravelines: 12 ms
- Strasbourg - Frankfurt: 4 ms
- Strasbourg - Wrocław: 24 ms
- Strasbourg - London: 15 ms
- London - Wrocław: 31 ms
- Europe - North America
- London - Beauharnois: 77 ms
- Wrocław - Beauharnois: 111 ms
- Strasbourg - Beauharnois: 91 ms
- Europe - Asia-Pacific
- Strasbourg - Singapore: 148 ms
- Strasbourg - Sydney: 288 ms
- Asia-Pacific - Asia-Pacific
- Sydney - Singapore: 149 ms
- Asia-Pacific - North America
- Singapore - Beauharnois: 234 ms
- Sydney - Beauharnois: 204 ms
By default, do instances automatically configure the address provided by DHCP?
Standard system images generally offer automatic configuration by DHCP on the instance’s first network interface. To configure additional interfaces, you will need to add them to the instance’s startup script, for example.