
A usecase posisble when operator wants to have a peering established per-VRF. This would mean, that they need to enslave a unique interface inside of the VRF and define peers for the router in FRR. Current logic with removal of the VRF upon disconnect makes such usecase impossible, as there are no means inside of the agent to recover FRR and VRF configuration to intended by operator state. This serves as motivation to allow operator to disable VRF removal through configuration option. Closes-Bug: #2097121 Change-Id: I2155508b167f84289de8f6510dfca1d5fc6a2a74
9 lines
356 B
YAML
9 lines
356 B
YAML
---
|
|
features:
|
|
- |
|
|
Added configuration option ``delete_vrf_on_disconnect`` which prevents
|
|
deletion of VRF from FRR and Linux kernel networking. This allows to
|
|
establish a peering session within VRF as well as externally enslave
|
|
additional interfaces into VRF in case EVPN integration with the rest of
|
|
infrastructure is not preferable.
|