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 OVH Public Cloud lets you design and build your network architecture on demand. By creating private networks, you implement virtual switches to connect your running project instances in real time, without any service interruptions.
Extended networks between regions
Public Cloud Private Networks are built on OVH vRack technology. This solution lets you build private networks between OVH datacentres, connecting instances across different regions around the world, privately and securely.
You can create up to 4,000 level 2 private networks. When you launch a Private Network, you create a new VLAN and only the resources connected to it can communicate with the VLAN. This isolation can be used to segment control plane and data plane networks.
Extension to other OVH services
You can also use the vRack to connect different OVH services to one another. For example, you can use your Private Network to connect your Public Cloud to your Private Cloud or Dedicated Services. This enables you to create the hybrid infrastructures you need, while keeping your 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.