Only routes learnt via SC should be contributors to aggregate route

[amit surana]

If a route-aggregate object is attached to a left interface of a SI, then only routes learnt via the SC (right VN routes) should be considered contributors to the aggregate route. At the moment, even local routes form the left VN are considered contributors.

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/17525
Submitter: Prakash Bailkeri (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/17567
Submitter: Prakash Bailkeri (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

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

commit c5a18cf0773b45cb48f1a1b0e1cc4b32ec2616ee
Author: Prakash Bailkeri <email address hidden>
Date: Mon Feb 22 11:26:22 2016 +0530

Trigger route aggregation on origin vn match

The more specific or contributing route to a route aggregate should have same origin
vn as what is calculated for aggregated route.

In case of route aggregation on service chain, the origin vn for aggregated route
is dest-vn of the service chain config. So contributing routes are considered
only if it re-originated/service chain route.

This fix ensure that route aggregation is triggered only with service chain routes

Added UT to validate service chain and route aggregation on routing instance object

Change-Id: Ifa210749def66b033400777e5d9d0c09ade65ebe
Closes-bug: #1547975

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/17567
Committed: http://github.org/Juniper/contrail-controller/commit/06b3e1480d6435fe634d2635bb8844a08e3b2574
Submitter: Zuul
Branch: R3.0

commit 06b3e1480d6435fe634d2635bb8844a08e3b2574
Author: Prakash Bailkeri <email address hidden>
Date: Mon Feb 22 11:26:22 2016 +0530

Trigger route aggregation on origin vn match

The more specific or contributing route to a route aggregate should have same origin
vn as what is calculated for aggregated route.

In case of route aggregation on service chain, the origin vn for aggregated route
is dest-vn of the service chain config. So contributing routes are considered
only if it re-originated/service chain route.

This fix ensure that route aggregation is triggered only with service chain routes

Added UT to validate service chain and route aggregation on routing instance object

Change-Id: Ifa210749def66b033400777e5d9d0c09ade65ebe
Closes-bug: #1547975
(cherry picked from commit c5a18cf0773b45cb48f1a1b0e1cc4b32ec2616ee)