Manage networks
Create bridge, OVN, macvlan, physical, and SR-IOV networks, view DHCP leases, attach instances, and peer OVN networks across projects.
Networks connect your instances to each other and, through NAT, to the internet. This page covers creating networks, the available network types, DHCP leases, attaching instances, and cross-project OVN peering.
Network types
You choose the network type when you create the network. The type cannot be changed afterwards — to switch types, create a new network and move your instances to it.
| Type | What it does |
|---|---|
| Bridge | A local virtual subnet that provides NAT, DHCP, and DNS to attached instances. The default choice for most workloads. |
| OVN | A distributed virtual subnet that provides NAT, DHCP, and DNS to attached instances. Requires an uplink network. OVN networks additionally support load balancers and cross-project peers. |
| Macvlan | Connects instances directly to an existing network interface, without a bridge. |
| Physical | Defines an uplink for OVN networks, or passes an existing physical interface through to a single instance. |
| SR-IOV | Connects instances to an existing SR-IOV-capable network interface. |
Networks that were not created through Akasha appear as unmanaged and are read-only: you can view their configuration but not change it.
Your project may limit how many networks you can create (limits.networks) and which networks or uplinks you are allowed to use. If the Create network button is unavailable, ask your administrator.
Create a network
- Go to Networking → Networks and click Create network.
- Select the network type.
- Enter a name (required) and an optional description.
- Configure addressing: for bridge and OVN networks, the IPv4 and IPv6 addresses can be
auto(an address range is assigned for you),none, or a custom CIDR, each with a NAT toggle. - Optionally adjust DHCP settings and ranges, DNS (domain, mode, search domains, nameservers), and MTU. Depending on the type, you can also set a VLAN ID and the parent interface to use.
- For bridge and OVN networks, you can attach network ACLs via the
security.aclsfield. - Click Create.
A YAML tab shows the full network configuration; use it to set options that are not exposed as form fields.
OVN uplinks
An OVN network needs an uplink — a managed bridge or physical network that carries its traffic out of the virtual network. Pick the uplink from the selector in the create form. The uplinks you can choose from may be restricted by your project configuration; if none are listed, ask your administrator.
Network detail tabs
Open a network from the list to see its detail page. The tabs depend on the type:
| Type | Tabs |
|---|---|
| Bridge | Configuration, Forwards, Leases |
| OVN | Configuration, Forwards, Load balancers, Leases, Peers |
| Other / unmanaged | Configuration only |
View DHCP leases
Bridge and OVN networks have a Leases tab that lists the DHCP leases the network has handed out — which instance holds which address. For a project-wide view of address usage across all networks, use the IPAM page.
Attach instances to a network
An instance connects to a network through a network device. Add one in the Devices → Network section of the instance configuration, or in a profile so that every instance using the profile is attached automatically. See Configure instances.
Cross-project peers (OVN)
An OVN network can be peered with an OVN network in another project, allowing traffic to flow between the two networks without leaving the platform. On the OVN network's Peers tab, create a peering by selecting the target project and its OVN network. Delete a peering from the same tab when you no longer need it. Cross-project peerings can be created and deleted only by an administrator — the target-project selector is limited to your own project otherwise. You can peer two OVN networks within your own project yourself; for a peering to another project, ask your administrator.