What I found:
1. Changes in reverse path filter behavior (8 to 9 or 9.0 to 9.1, couldn't tell). Fixed once, shouldn't repeat
2. East west traffic didn't work with some nodes or with specific segments or specific VMs. Happened several times. FRR...
sure, I've setup LUNs in passthrough mode in the past. I would like to avoid the LVM-PV-for-multiple-LVs route since the storage snapshots cannot be used.
I understand the single LUN + LVM value in some scenarios though.
the VLAN SDN zone already does the clusterwide syncing heavyweight lifting. nothing stops you from creating a script that polls VLAN list from the external source and uses native CLI tooling to add VLAN entries. Then, cron is your friend :)
That's an oddball. I have several doubts on option 1. Go with option 2 out of the two.
With 1GbE, I would separate management to avoid losing access when a workload misbehaves. Also, take into account that VM migrations will probably saturate...
Found several instances (in 8.* and 9.1) with unstable SDN environment. Updated my environments to 9.2, hope it gets better.
Born from the troubleshooting session: https://github.com/ciroiriarte/pve-tools/blob/master/pve-sdn-healthcheck
Hope it...
I'm working on a CLI tool (very early stages) to remotely interact with PVE and PDM, is anybody interested in something like this?, would love to receive some feedback:
https://github.com/ciroiriarte/pve-cli
I wonder what does "BGP Fabrics" bring to the table that EVPN/VLAN couldn't provide.
Would be great to be able to set VRF for physical node interfaces as exit point for BGP integrations.
Currently we have to set that up manually after zone...
I didn't add the config explicitly, it came from the SDN setup somehow.
For the time being I fixed it adding the option by hand, not sure if that is the correct approach.
Thanks.