Overview
Every project in Xloud Networking starts with a network — an isolated Layer 2 broadcast domain that instances attach to via virtual ports. Paired with a subnet, it defines the IP address space, DHCP assignment, and routing gateway for your workload tier.Prerequisites
- An active Xloud account with appropriate permissions
- Access to the Xloud Dashboard (
https://connect.<your-domain>) or CLI configured with credentials - API credentials sourced (
source admin-openrc.sh)
Create a Network and Subnet
- Dashboard
- CLI
Navigate to Networks
Log in to the Xloud Dashboard (
https://connect.<your-domain>) and navigate to
Project → Network → Networks.Configure the network
Fill in the Network tab:
| Field | Value | Description |
|---|---|---|
| Network Name | e.g., app-network | Display name for this network |
| Enable Admin State | Checked | Allow traffic through the network |
| Create Subnet | Checked | Configure an IP range in the next step |
| Availability Zone Hints | Optional | Pin to a specific availability zone if required |
Configure the subnet
Fill in the Subnet tab:
| Field | Value | Description |
|---|---|---|
| Subnet Name | e.g., app-subnet | Display name for this subnet |
| Network Address | e.g., 192.168.10.0/24 | CIDR block for the subnet |
| IP Version | IPv4 | Address family |
| Gateway IP | e.g., 192.168.10.1 | First-hop router IP (leave blank to auto-assign) |
Configure subnet details
Fill in the Subnet Details tab:
| Option | Recommendation |
|---|---|
| Enable DHCP | Enabled — lets instances receive IPs automatically |
| Allocation Pools | Leave blank to use the full CIDR range |
| DNS Name Servers | e.g., 8.8.8.8, 8.8.4.4 |
| Host Routes | Optional — inject static routes into DHCP clients |
Network Configuration Reference
| Parameter | Description | Default |
|---|---|---|
| Admin State | Controls whether the network is active and passes traffic | Enabled |
| MTU | Maximum transmission unit — set to 1450 for VXLAN networks | 1500 |
| Shared | Makes the network visible to all projects (admin only) | Disabled |
| External | Marks the network as a router external gateway target (admin only) | Disabled |
| DNS Domain | Enables DNS integration for hostname resolution | None |
Tenant networks created by regular users are automatically isolated to the project.
Only users with the
admin role can create shared or external provider networks.Validation
Confirm the network is operational before attaching instances.- Dashboard
- CLI
Navigate to Project → Network → Networks. The new network displays with:
- Status: Active
- Admin State: Up
- Subnets: Shows the configured CIDR
The network is ready to accept instance port attachments.
Next Steps
Create and Manage Subnets
Add additional subnets to your network for multi-tier isolation
Routers and Gateways
Connect your network to the external internet with an L3 router
Network Security Groups
Define firewall rules to control traffic to your instances
Floating IP Addresses
Allocate public IPs and associate them with your instances