Network Topology
The network topology view provides an interactive visualization of your virtual machines and their network connections.
Overview
The topology uses D3.js to render a force-directed graph showing:
- Virtual machines as nodes
- Networks as connection points
- Links between VMs and networks
Node Types
Virtual Machines
| Color | State |
|---|---|
| Green | Running |
| Gray | Stopped |
| Yellow | Starting/Stopping |
| Red | Error |
Networks
Orange nodes represent virtual networks:
- default - NAT network for internet access
- isolated - Private network for VM-to-VM communication
- bridged - Direct host network access
Routers
Blue nodes represent virtual routers (Elster OS VMs configured as routers).
Interaction
Mouse Controls
| Action | Effect |
|---|---|
| Click node | Select and show details |
| Drag node | Reposition in graph |
| Mouse wheel | Zoom in/out |
| Click + drag background | Pan view |
| Double-click | Center on node |
Node Details
Click a node to view:
- VM name and state
- IP addresses
- CPU/Memory allocation
- Connected networks
- Action buttons (Start, Stop, Console)
Hover Information
Hover over any node to see:
- Quick status summary
- Network connections
- Resource usage
Layout
Auto-Layout
The topology automatically arranges nodes using force simulation:
- Connected nodes cluster together
- Networks act as connection hubs
- Layout stabilizes after loading
Manual Arrangement
Drag nodes to create your preferred layout:
- Positions are preserved during session
- Reset layout with the refresh button
- Export layout for documentation
Network Configuration
Creating Networks
- Click Create Network button
- Enter network name
- Select network type:
- NAT (default)
- Isolated
- Bridged
- Configure IP range (optional)
- Click Create
Network Types
| Type | Description | Use Case |
|---|---|---|
| NAT | Network Address Translation | Internet access via host |
| Isolated | No external connectivity | Private VM networks |
| Bridged | Host network bridge | Direct network access |
Connecting VMs
When creating a VM, select networks to connect:
- Primary network (first interface)
- Additional networks (optional)
VMs can connect to multiple networks for complex topologies.
Example Topologies
Simple Server
[Internet] ── [NAT Network] ── [Web Server VM]Client-Server Testing
[Client VM] ─┬─ [Test Network] ─┬─ [Server VM]
│ │
└─── [NAT] ────────┘Multi-Tier Application
[Load Balancer] ── [Frontend Network] ── [Web VMs (x3)]
│
[Backend Network]
│
[Database VM]Filtering
Use the filter controls to:
- Show only running VMs
- Filter by network
- Search by name
- Show/hide networks
Export
Export the topology for documentation:
- PNG - Screenshot image
- SVG - Vector graphic
- JSON - Topology data
Real-Time Updates
The topology updates automatically when:
- VM state changes (start/stop)
- New VM created
- Network modified
- Connection changed
WebSocket connections ensure instant updates without refreshing.
Troubleshooting
Nodes Overlapping
Click the Reset Layout button to re-run the force simulation.
Missing Connections
Verify the VM has the network interface configured in libvirt.
Slow Performance
For large deployments (50+ VMs), consider:
- Filtering to relevant VMs
- Disabling animation
- Reducing update frequency