2415d30c0a
The handling of BVI is awkward, with the autoderived interface name "bviXX" based on the bridgedomain bd_id. Lots of special casing happens on account of this decision, and to make matters worse there is poor interaction (leading to VPP crashes) when BVIs and Loopbacks are used at the same time: https://lists.fd.io/g/vpp-dev/message/21116 In this commit, I reintroduce the ability to set bridgedomain virtual interfaces by means of the 'bvi' keyword. The 'bvi' must: - be a Loopback interface - must be used at most once (bvi_unique()) When pruning, I now need to prune bridgedomains before pruning loopbacks, because any given loopback might be a BVI for a bridge. So, I'll remove the loop/BVI from the bridge (by setting it to L3) and only then removing the loopback from VPP. In the reconciler, remove BVIs that have changed in prune_bridgedomains() and set it in sync_bridgedomains().
19 lines
355 B
YAML
19 lines
355 B
YAML
test:
|
|
description: "BridgeDomain BVIs must be unique"
|
|
errors:
|
|
expected:
|
|
- "bridgedomain .* BVI loop0 is not unique"
|
|
count: 2
|
|
---
|
|
loopbacks:
|
|
loop0:
|
|
description: "Cannot be BVI for both bd10 and bd11"
|
|
|
|
bridgedomains:
|
|
bd10:
|
|
description: "Bridge Domain 10"
|
|
bvi: loop0
|
|
bd11:
|
|
description: "Bridge Domain 11"
|
|
bvi: loop0
|