Do not associate OriginVn attribute to "Local"lly originated multicast route

[Ananth Suryanarayana]

Currently, OriginVn value is determined by looking at the virtual_network_index stored inside the routing-instance. Because it is possible that when RI is looked for the index, there may not be an index assigned yet, we some time end up attaching "0" as the originVn. This is incorrect and can cause issues during route imports and policy evaluations.

Similar to how other routes handled such as evpn, do not attach OriginVn attribute at all to the locally originated primary ermvpn route. Instead, evaluated based on route-target and attach to the secondary routes during replication.

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/32679
Submitter: Ananth Suryanarayana (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/32680
Submitter: Ananth Suryanarayana (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/32681
Submitter: Ananth Suryanarayana (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/32682
Submitter: Ananth Suryanarayana (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/32682
Committed: http://github.com/Juniper/contrail-controller/commit/50361eafda880382fe8763ffbf7905f84d614e5f
Submitter: Zuul (<email address hidden>)
Branch: R3.1

commit 50361eafda880382fe8763ffbf7905f84d614e5f
Author: Ananth Suryanarayana <email address hidden>
Date: Thu Jun 8 13:44:18 2017 -0700

Do not store OriginVn attribute in Locally originated multicast route

Currently, OriginVn value is determined by looking at the virtual_network_index
stored inside the routing-instance. Because it is possible that when RI is
looked for the index, there may not be an index assigned yet, we some time end
up attaching "0" as the originVn. This is incorrect and can cause issues during
route imports and policy evaluations.

Similar to how other routes handled such as evpn, do not attach OriginVn
attribute at all to the locally originated primary ermvpn route. Instead,
evaluated based on route-target and attach to the secondary routes during
replication.

Change-Id: I55c894f044b0b3bce537b9ace94cd836bfef0fa5
Closes-Bug: #1696853

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/32695
Submitter: Ananth Suryanarayana (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/32679
Committed: http://github.com/Juniper/contrail-controller/commit/0c456c401dbc8c6eac7b00e85898b0c77bb42319
Submitter: Zuul (<email address hidden>)
Branch: master

commit 0c456c401dbc8c6eac7b00e85898b0c77bb42319
Author: Ananth Suryanarayana <email address hidden>
Date: Thu Jun 8 13:44:18 2017 -0700

Do not store OriginVn attribute in Locally originated multicast route

Currently, OriginVn value is determined by looking at the virtual_network_index
stored inside the routing-instance. Because it is possible that when RI is
looked for the index, there may not be an index assigned yet, we some time end
up attaching "0" as the originVn. This is incorrect and can cause issues during
route imports and policy evaluations.

Similar to how other routes handled such as evpn, do not attach OriginVn
attribute at all to the locally originated primary ermvpn route. Instead,
evaluated based on route-target and attach to the secondary routes during
replication.

Change-Id: I55c894f044b0b3bce537b9ace94cd836bfef0fa5
Closes-Bug: #1696853

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/32680
Committed: http://github.com/Juniper/contrail-controller/commit/278949d8db6ede96d68db95d276ffb2a4168bb92
Submitter: Zuul (<email address hidden>)
Branch: R4.0

commit 278949d8db6ede96d68db95d276ffb2a4168bb92
Author: Ananth Suryanarayana <email address hidden>
Date: Thu Jun 8 13:44:18 2017 -0700

Do not store OriginVn attribute in Locally originated multicast route

Currently, OriginVn value is determined by looking at the virtual_network_index
stored inside the routing-instance. Because it is possible that when RI is
looked for the index, there may not be an index assigned yet, we some time end
up attaching "0" as the originVn. This is incorrect and can cause issues during
route imports and policy evaluations.

Similar to how other routes handled such as evpn, do not attach OriginVn
attribute at all to the locally originated primary ermvpn route. Instead,
evaluated based on route-target and attach to the secondary routes during
replication.

Change-Id: I55c894f044b0b3bce537b9ace94cd836bfef0fa5
Closes-Bug: #1696853

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/32681
Committed: http://github.com/Juniper/contrail-controller/commit/af4b66075ff10c9b23d4c01ff0d851e514704910
Submitter: Zuul (<email address hidden>)
Branch: R3.2

commit af4b66075ff10c9b23d4c01ff0d851e514704910
Author: Ananth Suryanarayana <email address hidden>
Date: Thu Jun 8 13:44:18 2017 -0700

Do not store OriginVn attribute in Locally originated multicast route

Currently, OriginVn value is determined by looking at the virtual_network_index
stored inside the routing-instance. Because it is possible that when RI is
looked for the index, there may not be an index assigned yet, we some time end
up attaching "0" as the originVn. This is incorrect and can cause issues during
route imports and policy evaluations.

Similar to how other routes handled such as evpn, do not attach OriginVn
attribute at all to the locally originated primary ermvpn route. Instead,
evaluated based on route-target and attach to the secondary routes during
replication.

Change-Id: I55c894f044b0b3bce537b9ace94cd836bfef0fa5
Closes-Bug: #1696853

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/32695
Committed: http://github.com/Juniper/contrail-controller/commit/f17813be5dd9d2b77c2153ca5652f343ed482486
Submitter: Zuul (<email address hidden>)
Branch: R3.1.1.x

commit f17813be5dd9d2b77c2153ca5652f343ed482486
Author: Ananth Suryanarayana <email address hidden>
Date: Thu Jun 8 13:44:18 2017 -0700

Do not store OriginVn attribute in Locally originated multicast route

Currently, OriginVn value is determined by looking at the virtual_network_index
stored inside the routing-instance. Because it is possible that when RI is
looked for the index, there may not be an index assigned yet, we some time end
up attaching "0" as the originVn. This is incorrect and can cause issues during
route imports and policy evaluations.

Similar to how other routes handled such as evpn, do not attach OriginVn
attribute at all to the locally originated primary ermvpn route. Instead,
evaluated based on route-target and attach to the secondary routes during
replication.

Change-Id: I55c894f044b0b3bce537b9ace94cd836bfef0fa5
Closes-Bug: #1696853
(cherry picked from commit 50361eafda880382fe8763ffbf7905f84d614e5f)