Network¶
Organization types and their connections¶
| Organization type | Who | Connections available |
|---|---|---|
| cloud | external clients | internet (inet), L2 channel (l2) |
| corporate | companies of the group | internet (inet), corporate network (corpnet), L2 channel (l2) |
An organization is corporate when its admin registers with an email domain from the corporate list, or when staff invite it as corporate.
Combining connections¶
Every project has at least one connection.
| Combination | Allowed |
|---|---|
inet |
yes |
corpnet |
yes (corporate projects) |
l2 alone |
yes, for cloud projects |
inet + l2 |
yes |
corpnet + l2 |
yes |
inet + corpnet |
no: the internet and the corporate network never exist in one project |
The portal assigns all addresses; the customer chooses the prefix sizes, from a list: /31, then /29, /28 … down to the largest block the site's IP subnets allow. The addresses come from the IP subnets of the site: public and corporate ranges recorded by the provider, each carried by one exchange network (an exchange network can carry several). For each public prefix the customer may also choose its base subnet, one of the subnets of the exchange networks the project's platform is on, or leave auto (the portal picks, cloud pools first).
Internet (inet)¶
flowchart TB
inet((Internet)) --- igwp["Internet gateways<br/>data network"]
igwp --- ix["Exchange network (IX)<br/>routers only"]
rr["Route reflectors"] -. BGP .- ix
ix --- egw["egw<br/>provider edge<br/>bandwidth, filtering"]
subgraph project ["Project resource pool"]
main["Main public network<br/>/31 and up"]
igw["igw<br/>project gateway"]
priv["Private networks<br/>SNAT"]
pub["Extra public networks"]
end
egw --- main --- igw
igw --- priv
igw --- pubflowchart TB
inet((Internet)) --- igwp["Internet gateways<br/>data network"]
igwp --- ix["Exchange network (IX)<br/>routers only"]
rr["Route reflectors"] -. BGP .- ix
ix --- egw["egw<br/>provider edge<br/>bandwidth, filtering"]
subgraph project ["Project resource pool"]
main["Main public network<br/>/31 and up"]
igw["igw<br/>project gateway"]
priv["Private networks<br/>SNAT"]
pub["Extra public networks"]
end
egw --- main --- igw
igw --- priv
igw --- pub
- The project's main public network is /31 or larger. Its first address is the egw, which is the project's default gateway; the next address is the igw. The main prefix can't be changed after the project is provisioned; it can only be replaced through a request.
- Extra public networks are routed through the igw.
- Bandwidth: 10 to 1000 Mbps.
Corporate network (corpnet)¶
flowchart TB
corp((Corporate network)) --- cgws["Corporate network gateways"]
cgws --- cix["Corporate exchange network"]
rr["Route reflectors"] -. BGP .- cix
cix --- cgw["cgw<br/>corporate edge, provider-controlled"]
subgraph project ["Project resource pool"]
cn["Corporate networks<br/>project prefixes"]
end
cgw --- cnflowchart TB
corp((Corporate network)) --- cgws["Corporate network gateways"]
cgws --- cix["Corporate exchange network"]
rr["Route reflectors"] -. BGP .- cix
cix --- cgw["cgw<br/>corporate edge, provider-controlled"]
subgraph project ["Project resource pool"]
cn["Corporate networks<br/>project prefixes"]
end
cgw --- cn
The same model as the internet: a dedicated exchange network with routers only, a provider-controlled edge (the cgw, one VyOS VM per project) with its outside leg in the exchange network and its inside legs in the project's corporate networks, and routes exchanged over BGP through the route reflectors. Internet access of a corporate project is controlled by the corporate network. The corporate network needs no igw.
The provider edge (egw)¶
The egw is the provider's VyOS VM, one per project and site. The project can't reach or change it.
- Bandwidth control: traffic is shaped to the ordered rate on both its sides: towards the exchange (the project's upload) and towards the project's main network (its download). Traffic inside the provider network is not limited.
- Traffic normalization: it lets in and out only the project's own public addresses (the main network and extra public networks), and drops addresses that aren't routed on the internet (RFC 1122, 1918, 3927, 5737, 6598 and other special-purpose blocks).
- It announces the project's public subnets to the route reflectors over BGP.
L2 channel (l2)¶
There are two kinds of L2 channel:
| Type | Joins | Approval |
|---|---|---|
| external | a VLAN from the client's site and a project network | a resource manager approves; support assigns the VLAN |
| internal | two of the project's own networks on two different sites | none to add; one channel per pair of sites, for a project with resources on two sites |
A project's L2 list shows each channel's type, endpoint 1, endpoint 2, MTU and state.
External channel¶
An external L2 channel extends a VLAN from the client's site into a project network over an L3 network: client systems and project VMs share one broadcast domain and one subnet.
flowchart TB
subgraph client ["Client site"]
cvlan["Client VLAN"]
end
subgraph mgmt ["Management platform"]
src["Leg 1 (src)<br/>bridge + VXLAN"]
end
subgraph payload ["Project's platform"]
dst["Leg 2 (dst)<br/>bridge + VXLAN"]
tnet["Project network<br/>VXLAN / EVPN"]
vms["Project VMs"]
end
cvlan ---|"VLAN, no IP"| src
src <-->|"VXLAN tunnel in WireGuard<br/>over the s2s transport network"| dst
dst --- tnet --- vmsflowchart TB
subgraph client ["Client site"]
cvlan["Client VLAN"]
end
subgraph mgmt ["Management platform"]
src["Leg 1 (src)<br/>bridge + VXLAN"]
end
subgraph payload ["Project's platform"]
dst["Leg 2 (dst)<br/>bridge + VXLAN"]
tnet["Project network<br/>VXLAN / EVPN"]
vms["Project VMs"]
end
cvlan ---|"VLAN, no IP"| src
src <-->|"VXLAN tunnel in WireGuard<br/>over the s2s transport network"| dst
dst --- tnet --- vms
- The channel has two provider-controlled legs. The legs exchange the client's Ethernet frames in a VXLAN tunnel; neither leg has an address in the client segment.
- Leg 1 faces the client site on the site's management platform. Leg 2 is one more VM in the project's network on the project's platform. A shared platform with a dedicated edge cluster bridges the VLAN with one VyOS VM there.
- A resource manager approves the channel and support assigns the VLAN number. The project binds the channel to one of its networks itself, and can change it later, without approval. The channel is made as soon as it has both.
- An external L2 channel can be the only connection of a cloud project, or go with the internet or the corporate network.
Internal channel¶
An internal L2 channel joins one of the project's networks on one site with one on another site, so that both are one broadcast domain over VXLAN. It is added on the project's L2 table (+ Internal channel: a name, the two sites and a network on each) and needs no approval; removing it does. It is offered only when the project has resources on two sites, and there is at most one internal channel per pair of sites.
Project gateway (igw)¶
The igw is the project's router between its private networks and the main public network. It is used with the internet connection; the corporate network and L2 channels need no igw.
| Type | What it is |
|---|---|
| advanced (VyOS) (default) | A VyOS router, created and set up for the project. Signed in to with ssh keys, or with a password when it was made without a key. |
| native (Service Virtual Router) | The OpenNebula Service Virtual Router. |
| custom (your own VM) | The project's own VM in the igw role, given the igw address. |
- The igw always runs inside the project's resource pool: it is the project's VM, owned by the project admin, and it uses the project's resources.
- Private networks behind it reach the internet through address translation (SNAT).
- The type can be changed later, without approval; the igw is then replaced, its configuration is not kept, and it keeps its address.
Details: Network design.