To handle EVPN Type-5 prefixes, all L2 virtual-networks are to be associated
with a single L3VRF virtual-network. This is used to route packets for all
children L2 virtual-networks.
There already exists a link between logical-router and virtual-network. In this
schema change, this link is annotated with attributes so that the relationship
can be futher qualified. This attribute defaults to existing behavior as
ExternalGateway. Additional L2VN and L3VN types are added to this link attribute.
Reviewed: https:/ /review. opencontrail. org/39167 github. com/Juniper/ contrail- controller/ commit/ 0f3fbb053928a66 4c362f123ace7f0 aea9f0ff08
Committed: http://
Submitter: Rudra Rugge (<email address hidden>)
Branch: master
commit 0f3fbb053928a66 4c362f123ace7f0 aea9f0ff08
Author: Ananth Suryanarayana <email address hidden>
Date: Thu Jan 25 12:01:40 2018 -0800
Schema changes for Type-5 EVPN
To handle EVPN Type-5 prefixes, all L2 virtual-networks are to be associated
with a single L3VRF virtual-network. This is used to route packets for all
children L2 virtual-networks.
There already exists a link between logical-router and virtual-network. In this
schema change, this link is annotated with attributes so that the relationship
can be futher qualified. This attribute defaults to existing behavior as
ExternalGateway. Additional L2VN and L3VN types are added to this link attribute.
Change-Id: I560596afb5f16e 77c48b1ae926e60 8afd5c8c504 756c0d72ab2088c 033356de747 /blueprints. launchpad. net/opencontrai l/+spec/ evpn-type- 5
Depends-On: I0aa35f774bab5f
Implements: blueprint https:/
Partial-bug: 1636654