Skip to content
Cloudbricks.dev logo

Apache CloudStack — Networking Models

Part 3 of the Apache CloudStack series: basic vs advanced networking, VLANs, VPCs, L2 networks, and network offerings.

Kishore 5 min read

Networking is where most CloudStack installations are won or lost. Compute and storage can be fixed after the fact; a zone built on the wrong networking model is usually a rebuild.

This part covers the two zone models, how CloudStack isolates tenant traffic, and how to choose a network offering that matches what you are trying to build.

Basic vs advanced networking

CloudStack gives you two ways to build a zone, and the choice is made when the zone is created.

Basic zoneAdvanced zone
Tenant isolationNone — one shared guest networkVLAN or VXLAN per account/network
Typical useDev/test, small private cloudsProduction, multi-tenant, service providers
VPC supportNoYes
RouterNot required for the shared networkVirtual router per isolated network/VPC
Security groupsYes, on the shared networkYes, plus network ACLs for VPC tiers
ComplexityLowHigh

In a basic zone, every instance sits on the same L2 segment. Users can reach each other unless security groups say otherwise. It is simple, fast to stand up, and fine for a lab or an internal cloud where tenants are trusted.

In an advanced zone, each account gets isolated networks. CloudStack allocates a VLAN (or VXLAN VNI) from the range you configure, and a virtual router provides DHCP, DNS, source NAT, and routing between tiers. This is the model you need for VPCs and for any real multi-tenant deployment.

The physical network

Before you create guest networks, CloudStack needs to know about the physical network underneath. In the zone wizard this is the physical network with one or more traffic types:

  • Management — communication between the management server and the hypervisors.
  • Public — the addresses used for public IPs and floating IPs.
  • Guest — the VLAN/VXLAN range used for tenant networks.
  • Storage — optional separate network for primary/secondary storage.

Each traffic type is mapped to a label on the hypervisor bridges. On KVM, the labels must match the bridges you configured on the host. A mismatch here is the classic “zone created, instances cannot reach anything” failure.

A typical advanced-zone guest range looks like this:

Guest VLAN range: 200-299
Physical network label: cloudbr0
Public range: 192.168.10.50-192.168.10.99
Management: 192.168.10.10-192.168.10.20

Document the ranges before you start. Overlapping them with your lab LAN is a painful mistake to unwind.

Network offerings

A network offering is the template that tells CloudStack which services a network should provide and which plugin implements them. The common ones are:

  • Shared network — a flat network available to multiple accounts. No isolation. Basic zones use this.
  • Isolated network — a per-account network with its own VLAN/VXLAN and virtual router. Advanced zones use this.
  • L2 network — a network that extends an existing VLAN into CloudStack without a virtual router. Useful when an external device does the routing.
  • VPC offering — a container for multiple isolated tiers that share a router and a public IP.

You can list what your installation offers with:

cmk list networkofferings

Read the name, guestiptype, supportedservices, and forvpc fields. Do not assume every offering is available in every zone; the offering must be compatible with the zone’s networking model.

Creating a tenant network

The exact IDs differ per installation. Get them first:

cmk list zones
cmk list networkofferings

Then create an isolated network:

cmk create network \
  name=app-tier \
  displaytext="Application tier" \
  zoneid=<zone-id> \
  networkofferingid=<isolated-offering-id>

CloudStack allocates a VLAN from the guest range and deploys a virtual router. Confirm it worked:

cmk list networks zoneid=<zone-id>
cmk list routers

The router should reach the Running state. If it does not, the usual causes are a missing template, an unreachable management network, or a hypervisor that cannot start the system VM.

VPCs and tiers

A VPC is a set of isolated tiers that share a router and a public IP. The pattern is:

  1. Create a VPC offering and a VPC.
  2. Create one or more tiers inside the VPC, each with its own CIDR.
  3. Add a public IP to the VPC.
  4. Create an egress/ingress rule or a port-forwarding rule.
cmk create vpc \
  name=prod-vpc \
  displaytext="Production VPC" \
  zoneid=<zone-id> \
  vpcofferingid=<vpc-offering-id> \
  cidr=10.10.0.0/16
cmk create network \
  name=web-tier \
  displaytext="Web tier" \
  zoneid=<zone-id> \
  networkofferingid=<vpc-tier-offering-id> \
  vpcid=<vpc-id> \
  gateway=10.10.1.1 \
  netmask=255.255.255.0

VPC tiers are where network ACLs matter. Security groups apply to individual instances; ACLs apply to the tier and are evaluated before the instance is reached.

Choosing a model

Use a basic zone when:

  • You are learning CloudStack or building a lab.
  • All users are trusted and do not need isolation.
  • You want the simplest possible path to a running VM.

Use an advanced zone when:

  • You need per-account isolation or VPCs.
  • You are hosting workloads for more than one team or customer.
  • You need controlled public IP allocation and NAT.

You can run both models in the same CloudStack installation, in separate zones. That is useful in a lab: a basic zone for quick tests, an advanced zone for the networking material.

Troubleshooting checklist

  • Instances get an IP but cannot reach the gateway. Check the virtual router state and the guest VLAN/bridge mapping on the host.
  • No DHCP lease. The router’s DHCP service may not be running; check the router’s system VM console and logs.
  • Floating IP does not work. Confirm the public VLAN is trunked to the host and that the public range is routed to CloudStack.
  • VPC tier creation fails. The tier CIDR must sit inside the VPC CIDR and must not overlap another tier.
  • Network offering missing. The offering must be compatible with the zone type and the hypervisor plugin.