Closed glimchb closed 1 year ago
Yes @glimchb as I have explained before maybe this is something that is missing from the API as the VRF spec have VTEP IP but the LogicalBridgeSpec it doesn't. Maybe we need to add this VTEP IP field to the API or completely remove it also from the VRF spec and pass it in both cases through evpn-gw-br configuration files. I will need to discuss this with @JanScheurich before we do any changes to the API. For now when it comes to the LogicalBridges you can pass the VTEP IP through configuration in evpn-gw-br.
thanks @mardim91 I will leave this issue open for tracking
@JanScheurich please advise
The optional VTEP IP is indeed missing from the LogicalBridgeSpec (We have it in the VrfSpec for L3 EVPN). It was simply forgotten when extending to the L2 EVPN use case. We never actually used it in our prototype because our server implementation had a default VTEP configured. Please go ahead and create an API PR to add the vtep_id_prefix as optional argument.
opened https://github.com/opiproject/opi-api/pull/349 please review
I see no field for IP address
but
see hard-coded https://github.com/opiproject/opi-evpn-bridge/blob/b998cfea409b9e05dc38e608288d9e1b8f649590/pkg/evpn/bridge.go#L72-L73
@mardim91 please advise