Skip to content
Portal

Cloudspace Networking Deep Dive

This page covers the advanced networking capabilities within a cloudspace: port forwards, network routes, external networks, connected cloudspaces, anti-affinity groups, and per-cloudspace roles.

For basic cloudspace creation and management, see Cloudspaces.

Port Forwards

A port forward maps a port on the cloudspace's external virtual firewall to a port on a target resource inside the cloudspace — a virtual machine or a nested cloudspace.

Creating a port forward

  1. Navigate to the cloudspace details page and select Port forwards from the MORE menu.
  2. Click CREATE PORT FORWARD.
  3. Configure:
    • From IP address (optional — if left empty the cloudspace's external IP is used) and External virtual firewall port — use Configure forwarding for a range of ports to specify a start and end port and forward a whole range at once.
    • To — a Virtual machine or a Nested cloudspace virtual machine — the VM and its VM port (also start/end for a range).
    • Protocol — TCP or UDP.
  4. Click CREATE.

Port forwards aren't supported for private cloudspaces, since they have no external virtual firewall to forward from.

Updating or deleting a port forward

Open the port forward from the list to edit its fields, or use the delete icon on its row to remove it. The Delete port forward dialog asks you to confirm and needs no reason.

Network Routes

Network routes define static routes from the cloudspace to destinations not reachable via the default gateway.

Adding a network route

  1. Navigate to the cloudspace details page and select Network Routes from the More dropdown menu.
  2. Click ADD NETWORK ROUTE.
  3. Configure:
    • Destination — the network to route.
    • Gateway — the next-hop address to route the destination over.
    • Metric (optional, default 500) — the lowest value has the highest priority.
    • Table (optional) — the routing table to store the route in. Leave it empty to use the default table.
  4. Click ADD NETWORK ROUTE.

Deleting a network route

Select the route from the list and use the delete action.

External Networks

An external network is a network outside the cloudspace, such as the internet or your company network, that your operator makes available at the location (customers cannot add them). A cloudspace whose virtual firewall is connected to one is public; public does not necessarily mean connected to the internet.

An external network gives the cloudspace's virtual firewall an interface inside a target network — either an external network attached to the location, or another cloudspace.

Adding an external network

  1. Navigate to the cloudspace details page and select the External Networks tab.
  2. Click ADD EXTERNAL NETWORK.
  3. Choose the type (external network or cloudspace), the target network, and optionally a Metric (lowest value has highest priority) and IP address.
  4. Click ADD EXTERNAL NETWORK.

Deleting an external network

Select the external network from the list and use the remove action.

Connected Cloudspaces

Connecting two cloudspaces lets VMs in each reach the other over their private networks, without routing through an external network.

Note

Connected cloudspaces aren't supported for private or nested cloudspaces, and the two cloudspaces must not have overlapping private networks.

Connecting cloudspaces

  1. Navigate to the cloudspace details page and select Connected Cloudspaces from the MORE menu.
  2. Click CONNECT TO REMOTE CLOUDSPACE.
  3. On the Select remote cloudspace step, select the target cloudspace (table columns Target cloudspace and Location). The list only shows public cloudspaces other than the current one, and NEXT stays disabled until you choose one.
  4. On the Select IP address endpoints step, choose the endpoints and finish the wizard.

Disconnecting cloudspaces

Select the connection from the list and use the disconnect action.

Nested Cloudspaces

A nested cloudspace is structurally different from a connected one: its virtual firewall's external interface sits inside its parent cloudspace's private network, rather than on an external network. This is a parent-child hierarchy set once, at creation time — choose To another cloudspace in this location as the connectivity type and pick the parent — not something you connect or disconnect afterwards.

Every cloudspace has a Nested Cloudspaces page (in the MORE menu) listing the cloudspaces nested underneath it (its children), regardless of whether the cloudspace itself is public, private, or nested:

Column Shows
Name The nested cloudspace's name — links to its own details page
Parent IP The nested cloudspace's IP address inside this cloudspace's private network
Private network The nested cloudspace's own subnet

This page is read-only — there's no create/connect/disconnect action here, and it shows No nested cloudspaces available when there are none. If a cloudspace is itself nested, its own details panel shows a Parent Cloudspace field linking up to its parent.

Note

This is unrelated to Connected Cloudspaces above — nesting is a fixed hierarchy chosen at creation, while connecting is an opt-in peering between two independent, non-nested cloudspaces.

Connected VMs

The Connected VMs page (in the MORE menu) is a read-only report, not an action screen: it lists individual VMs — which may live in a different cloudspace entirely — that have a network interface attached directly to this cloudspace's network.

Column Shows
Virtual machine The connected VM's name — links to its own details page
Cloudspace The VM's home cloudspace — links to that cloudspace
IP address/es The VM's IP address(es) on this cloudspace's network
Status The VM's current status

The page shows No connected virtual machines available when there are none. There's no connect/disconnect action on this page. The connection itself is made from the other side, using External Networks above: when adding an external network to a cloudspace, choosing a target type of cloudspace gives every VM there a route into it. A VM's own network interfaces (its "Network Interfaces" tab) can similarly be configured with an interface directly into another cloudspace's network. Either way, that VM then shows up here, on the cloudspace it's now connected to.

Anti-Affinity Groups

Anti-affinity groups place a group of VMs across different physical hosts, so a single host failure doesn't take down every VM in the group at once.

Creating an anti-affinity group

  1. Navigate to the cloudspace details page and select Anti-affinity groups from the MORE menu.
  2. Click CREATE ANTI-AFFINITY GROUP.
  3. Enter a Label and a Spread value — or check infinite spread to keep every VM in the group on a separate host.
  4. Click CREATE.

Adding or removing VMs

Open the group and use Add virtual machine to add a VM, or the delete action next to a VM in the group's list to remove it.

Deleting an anti-affinity group

Select the group from the list and use the delete action.

Per-Cloudspace Roles

A cloudspace has its own Roles & permissions page (in the MORE menu), listing the custom roles — created under Roles & Permissions — that have been granted access to this specific cloudspace, with their assigned permissions.

Note

Roles themselves are created once, under the customer's Roles section, then granted access to individual resources — a cloudspace, a VM, a disk, and so on. This page shows and manages the grants for one cloudspace; it isn't where roles are defined.

Grant a role access to the cloudspace, or remove an existing grant, from this page. See Roles & Permissions for how roles and their permissions are defined.