Don't copy export-only RT of VN to export-list of SI RI

[amit surana]

Consider a hub-and-spoke topology, where spoke VNs are exporting their routes with RT-1 and importing only hub VN routes via RT-2. Now, if one of the spoke VNs is connected via a service-chain to another spoke VN (or some other non-spoke VN), both the SI RIs copy the export-only RT, RT-1, from the VNs to their respective export-list. This will cause the hub VN to see 2 routes to the spoke VNs: one direct route (from importing RT-1 from the spoke VNs) and another via the SC re-originated route which also has RT-1. This is undesirable.

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/17660
Submitter: Sachin Bansal (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/17714
Submitter: Sachin Bansal (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

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

commit e4bdb03ef4007e9a8d9546f40cbb138556f97ec1
Author: Sachin Bansal <email address hidden>
Date: Mon Feb 22 14:44:24 2016 -0800

Use import-only/export-only route targets only for primary RI

They are created primarily for hub-spoke topologies. Using them for
service instances/logical routers/transit networks causes unexpected
behavior. Restrict their usage to primary RI only.

Change-Id: I72bd3a78a96c4a3872788fce2c00113ea388e9ec
Closes-Bug: 1547933
Closes-Bug: 1547930

[OpenContrail Admin (ci-admin-f)]

Reviewed: https://review.opencontrail.org/17714
Committed: http://github.org/Juniper/contrail-controller/commit/66cba1dbb520fbb8665de96b09a7f639f5d6ed61
Submitter: Zuul
Branch: R3.0

commit 66cba1dbb520fbb8665de96b09a7f639f5d6ed61
Author: Sachin Bansal <email address hidden>
Date: Mon Feb 22 14:44:24 2016 -0800

Use import-only/export-only route targets only for primary RI

They are created primarily for hub-spoke topologies. Using them for
service instances/logical routers/transit networks causes unexpected
behavior. Restrict their usage to primary RI only.

Change-Id: I72bd3a78a96c4a3872788fce2c00113ea388e9ec
Closes-Bug: 1547933
Closes-Bug: 1547930
(cherry picked from commit e4bdb03ef4007e9a8d9546f40cbb138556f97ec1)