[R 2.20]DM: L3 Vrf not created on MX for contrail VNs

[amit surana]

Tracking 2 issues with this bug:

1. For every contrail VN, a L2 virtual-switch (evpn) and L3 VRF should be created on the MX. Currently, only the virtual-switch is created.

2. The IRB interface should be dropped into the L3 VRF.

root# show routing-instances
evpn-inet1 {
    instance-type vrf;
    interface si-0/0/0.1;
    interface irb.0;
    vrf-import import-inet;
    vrf-export export-inet1;
    vrf-table-label;
    routing-options {
        inactive: static {
            route 0.0.0.0/0 next-hop si-0/0/0.1;
        }
        router-id 11.1.10.1;
        auto-export {
            family inet {
                unicast;
            }
        }
    }
}
evpn-vxlan1 {
    description vxlan;
    vtep-source-interface lo0.1;
    instance-type virtual-switch;
    route-distinguisher 64512:10000;
    vrf-target target:64512:10000;
    protocols {
        evpn {
            traceoptions {
                file evpn-vxlan1.log;
                flag all;
            }
            encapsulation vxlan;
            extended-vni-list all;
        }
    }
    bridge-domains {
        bd1 {
            domain-type bridge;
            vlan-id 10;
            interface xe-0/3/0.0;
            routing-interface irb.0;
            vxlan {
                vni 100;
            }
        }
    }
}

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/11533
Submitter: Suresh Balineni (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/11534
Submitter: Suresh Balineni (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/11533
Submitter: Suresh Balineni (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/11534
Submitter: Suresh Balineni (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/11534
Committed: http://github.org/Juniper/contrail-controller/commit/3e81f8191a7cf3102ce0d87e9eee23a2fe83e907
Submitter: Zuul
Branch: master

commit 3e81f8191a7cf3102ce0d87e9eee23a2fe83e907
Author: sbalineni <email address hidden>
Date: Thu Jun 11 18:38:33 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.
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()

Change-Id: I7821aa535622df9ce7ee780fd6a44abc680aaec8
Closes-Bug: #1464446
Closes-Bug: #1464786

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/11533
Committed: http://github.org/Juniper/contrail-controller/commit/008791a80e3e483f720e50ac3198f0c44aa71738
Submitter: Zuul
Branch: R2.20

commit 008791a80e3e483f720e50ac3198f0c44aa71738
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.
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()

Closes-Bug: #1464446
Closes-Bug: #1464786

Change-Id: I6eb9763342631ba6a9235cc4145ea180604e5c8a