Network automation

Built for software networks

VMease uses Proxmox Software-Defined Networking (SDN) to provide VXLAN-backed virtual networks for tenant and workload connectivity.

When setting up the platform, VMease creates the site SDN zone for VXLAN networking. It finds the Proxmox hosts in the cluster, builds the VXLAN peer list from host management addresses, updates the SDN zone if needed, and applies the Proxmox SDN configuration so the overlay network works across the cluster.

This provides the platform with a stable network foundation for tenant VNETs. Instead of setting up each virtual network by hand, VMease handles zone and virtual network configuration, providing the functionality to admins and users.

VXLAN inventory

VMease network model treats virtual networks like inventory.

When a new VNET is needed, VMease checks if there is already an available Proxmox SDN VNET in the right cluster and VXLAN zone. If so, it assigns that VNET to the requested logical network.

If no spare VNET is available, VMease can automatically create a new batch of SDN VNETs. These are set up in Proxmox, given unique names and VXLAN tags, stored in the VMease inventory, and made ready for assignment.

This method makes operations more reliable because the platform keeps a pool of known network resources. It also speeds up the user experience and minimises system changes. Users can request a network from the portal, and the platform handles SDN allocation, naming, tagging, and activation.

When a logical VNET is deleted, VMease does not remove the physical Proxmox SDN network. Instead, it can unassign the VNET and return it to the available inventory. This spare-pool model lets network resources be reused easily without extra changes to the underlying setup.

VMease does more than create virtual networks. It also finds and maps out the physical host networking that supports those virtual networks.

The platform scans Proxmox host network configuration and classifies interfaces into meaningful categories, including physical or Layer 2 interfaces, Layer 3 interfaces with IP configuration, and Linux bridges.

This gives VMease a clear view of how each Proxmox host is set up. Rather than treating host networking as an individual config file, the platform turns it into useful inventory. This inventory enables automation that needs to know what each interface does. A host might have interfaces for management, storage, tenant traffic, external connections, cluster traffic, or VM bridge access. VMease tracks these roles so automation can make safe, consistent choices later.

Host NIC templates

Hybrid virtual and physical network model

VMease supports both VLAN-backed and VXLAN-backed network constructs.

VLAN networks work well when there is already physical network segmentation, switch setup, routed networks, or outside connectivity needs. VXLAN-backed VNETs are useful for scalable overlay networking across a Proxmox cluster, especially when tenant networks need to be created quickly and consistently.

Both types are handled by the VMease network model, so higher-level platform features can use them without users needing to know all the technical details each time. Workloads can be connected to a VLAN network or a VNET network. VMease then manages the correct Proxmox attachment: VLAN networks use the right bridge and VLAN tag, while VNET networks use the assigned SDN VNET bridge.

This lets administrators stay flexible and maintain control.

Designed for self service

In a multi-tenant private cloud, network automation needs to do more than just create a bridge or tag a VLAN. It also has to keep accounts, quotas, sites, and workloads separate.

VMease links network allocation to the compute quota and cluster context. When a tenant or delegated account requests a VNET, the platform resolves the correct cluster from the quota relationship and assigns a network from the right Proxmox SDN inventory.

This helps ensure network resources are given out within the right infrastructure limits. It also supports delegated administration, so users can use approved network features without needing full access to Proxmox, Linux networking, or upstream setup.

Integrated with firewall automation

The VMease network model also underpins the firewall automation layer. When a VyOS firewall is provisioned, VMease can attach firewall interfaces to the requested VLANs or VNETs. For VLAN networks, the platform identifies the correct bridge and applies the VLAN tag. For VNET networks, it finds the assigned SDN VNET bridge and attaches the firewall directly to it.

VMease then records the resulting interface details, including the Proxmox interface, the VyOS interface, the friendly interface name, MAC address, network type, VLAN or VNET reference, and assigned IP address.

This sets up a clear process from the network request to the firewall interface setup.

Operationally visible and task-driven

Network changes in VMease are processed through the same task-driven control-plane model used across the wider platform.

A network automation daemon receives requests, runs them in the background, handles each resource as needed, and returns clear status and response data. This approach is more reliable than making changes directly through the GUI.

For administrators, this means network operations can be tracked, audited, and checked. The platform can show what was requested, what was assigned, which cluster and SDN zone were used, whether a new VNET batch was created, and the final result.

If something goes wrong, VMease logs the failure and tries to clean up network records, so users are not left with confusing or leftover entries in the interface.

Summary

VMease network automation is designed to make private cloud networking easier and less of a hassle. Instead of having admins manually set up Proxmox SDN, VXLAN zones, Linux bridges, VLAN tags, firewall interfaces, and tenant network records, VMease brings all these parts into one managed platform workflow.

VMease gives organisations the flexibility of private infrastructure along with the smooth experience of a cloud platform.