Add EVPN-VPWS to L2VPNTypeChoices #17694
Conversation
There was a problem hiding this comment.
Just to leave a little background on the PR. While a VPWS is a Point-to-Point protocol, current in NetBox we have no way to properly model the relationship between two devices that are part of a MC-LAG using EVPN ESI (The chassis' don't talk to each other over a MC-LAG protocol, they use EVPN to build the MC-LAG; I believe technically a chassis could be part of an MC-LAG with one device on one bundle and then part of a different MC-LAG with a different bundle, but I haven't dove too far into it)
So you would either need to model two VPWS and link them together (maybe a parent/child relationship), build a new model to bridge the two devices for MC-LAG or allow a multi-connect like this. I think this is the more reasonable way to handle it for no, anything else would require substantial effort.
* Add EVPN-VPWS to the availbable L2VPN Connection Types * Updated documentation to reference the new L2VPN type.
* Add EVPN-VPWS to the availbable L2VPN Connection Types * Updated documentation to reference the new L2VPN type.
Fixes: #17216
Updated L2VPNTypeChoices to include the EVPN-VPWS type but didn't include it in the P2P list so more than two interfaces can be assigned to it.