l3 vrf and l2 evpn vrf config both need to be configured
Currently, DM configures only one vrf for a a virtual network either l2 evpn or
l3 vrf config but not both depending on the vxlan vni identifier.
It must configure both for a private network.
For a public network, only l3 vrf config is required.
import-export statment is not required for l2 vrf.
UT tests for these modifications are tracked in https://bugs.launchpad.net/juniperopenstack/+bug/1464792
Fixed the issue - self paramter is minning in get_commit_stats()
Reviewed: https:/ /review. opencontrail. org/11533 github. org/Juniper/ contrail- controller/ commit/ 008791a80e3e483 f720e50ac3198f0 c44aa71738
Committed: http://
Submitter: Zuul
Branch: R2.20
commit 008791a80e3e483 f720e50ac3198f0 c44aa71738
Author: sbalineni <email address hidden>
Date: Thu Jun 11 18:32:15 2015 -0700
l3 vrf and l2 evpn vrf config both need to be configured
Currently, DM configures only one vrf for a a virtual network either l2 evpn or
l3 vrf config but not both depending on the vxlan vni identifier.
It must configure both for a private network. /bugs.launchpad .net/juniperope nstack/ +bug/1464792
For a public network, only l3 vrf config is required.
import-export statment is not required for l2 vrf.
UT tests for these modifications are tracked in https:/
Fixed the issue - self paramter is minning in get_commit_stats()
Closes-Bug: #1464446
Closes-Bug: #1464786
Change-Id: I6eb9763342631b a6a9235cc4145ea 180604e5c8a