Files
loc_az_hci/infrastructure/network/ip-schema-config.yaml
defiQUG c39465c2bd
Some checks failed
Test / test (push) Has been cancelled
Initial commit: loc_az_hci (smom-dbis-138 excluded via .gitignore)
Co-authored-by: Cursor <cursoragent@cursor.com>
2026-02-08 09:04:46 -08:00

131 lines
3.8 KiB
YAML

# IP Address Allocation per VLAN
# Schema: 10.10.x.0/24 for each VLAN
# Proxmox Host Network Configuration
# Both ML110 and R630 Proxmox servers use a simple two-NIC configuration:
#
# vmbr0 (LAN Bridge):
# - Connected to NIC 1
# - Network: 192.168.1.0/24
# - IP assignment: DHCP (from local router/switch)
# - Purpose: Management network, VM connectivity on LAN
# - Route metric: 200 (lower priority for default route)
#
# vmbr1 (WAN Bridge):
# - Connected to NIC 2
# - Network: Public IP via DHCP from Spectrum cable modem
# - IP assignment: DHCP (direct from Spectrum modem)
# - Purpose: Public internet access, VM connectivity on WAN
# - Route metric: 100 (higher priority for default route)
#
# Note: All IP addresses for Proxmox hosts are assigned via DHCP.
# The actual IP addresses will vary based on DHCP server assignments.
vlans:
- id: 10
name: storage
subnet: "10.10.10.0/24"
gateway: "10.10.10.1"
description: "Core storage, shelves, NAS services"
allocations:
- ip: "10.10.10.1"
device: "Router server storage interface"
- ip: "10.10.10.10"
device: "NAS services"
- ip: "10.10.10.20"
device: "Backup services"
range: "10.10.10.1-10.10.10.254"
- id: 20
name: compute
subnet: "10.10.20.0/24"
gateway: "10.10.20.1"
description: "Hypervisor traffic, Proxmox migrations"
allocations:
- ip: "10.10.20.1"
device: "Router server compute interface"
- ip: "10.10.20.10"
device: "HPE ML110 Gen9 (Note: Actual Proxmox host uses 192.168.1.x via DHCP on vmbr0)"
- ip: "10.10.20.20"
device: "Dell R630 (Note: Actual Proxmox host uses 192.168.1.x via DHCP on vmbr0)"
range: "10.10.20.1-10.10.20.254"
- id: 30
name: app_tier
subnet: "10.10.30.0/24"
gateway: "10.10.30.1"
description: "Web/API, internal apps"
allocations:
- ip: "10.10.30.1"
device: "Router server app interface"
- ip: "10.10.30.10"
device: "Reverse proxy"
- ip: "10.10.30.20-50"
device: "Application services"
range: "10.10.30.1-10.10.30.254"
- id: 40
name: observability
subnet: "10.10.40.0/24"
gateway: "10.10.40.1"
description: "Monitoring, logging"
allocations:
- ip: "10.10.40.1"
device: "Router server monitoring interface"
- ip: "10.10.40.10"
device: "Prometheus"
- ip: "10.10.40.20"
device: "Grafana"
- ip: "10.10.40.30"
device: "Loki/OpenSearch"
range: "10.10.40.1-10.10.40.254"
- id: 50
name: dev_test
subnet: "10.10.50.0/24"
gateway: "10.10.50.1"
description: "Lab workloads"
allocations:
- ip: "10.10.50.1"
device: "Router server dev interface"
- ip: "10.10.50.10-30"
device: "Dev VMs"
- ip: "10.10.50.40-60"
device: "Test VMs"
- ip: "10.10.50.70"
device: "CI/CD services"
range: "10.10.50.1-10.10.50.254"
- id: 60
name: management
subnet: "10.10.60.0/24"
gateway: "10.10.60.1"
description: "WAC, Azure Arc, SSH, hypervisor mgmt"
allocations:
- ip: "10.10.60.1"
device: "Router server management"
- ip: "10.10.60.10"
device: "Jump host"
- ip: "10.10.60.20"
device: "Windows Admin Center"
- ip: "10.10.60.30+"
device: "Azure Arc agents"
range: "10.10.60.1-10.10.60.254"
- id: 99
name: dmz
subnet: "10.10.99.0/24"
gateway: "10.10.99.1"
description: "Proxies, bastions, Cloudflare tunnel hosts"
allocations:
- ip: "10.10.99.1"
device: "Router server DMZ interface"
- ip: "10.10.99.10"
device: "Cloudflare Tunnel VM"
- ip: "10.10.99.20"
device: "Reverse proxy"
- ip: "10.10.99.30"
device: "Bastion host"
range: "10.10.99.1-10.10.99.254"