CONTRAILEN-168: RD Collision with Compute Node IP Address Reuse

[SANDEEP SHAH]

User-defined RD range to avoid duplicates across AIC sites

As compute host IPv4 addresses are reused across clusters (e.g., large AIC sites), we need support for user-defined RD range which can allow for customization of IP address field in Type-1 RD used by Contrail.

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/30484
Submitter: SANDEEP SHAH (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

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

commit 052f9b22412ba92fb46526050579c7c865d28878
Author: sandeepopenstack <email address hidden>
Date: Sun Apr 16 03:09:09 2017 -0500

Specs to address an issue with RD Collision

In large scale Contrail deployments, Compute IP addresses are often
reused across data centers. This poses a RD collision problem when these
data centers are inter-connected through a hierarchical BGP topology.
This spec describes an implementation plan to address this problem. The
proposal will still generate a Type 1 RD.

Partial-Bug: #1679198

Change-Id: I23b381b0f09bb9b7a3493dff6fd7f9dd3f5c7edb

[OpenContrail Admin (ci-admin-f)]

Review in progress for https://review.opencontrail.org/34158
Submitter: SANDEEP SHAH (<email address hidden>)

[OpenContrail Admin (ci-admin-f)]

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

commit 0266efd10773a03334df74f92794911b44c8c5fa
Author: Sandeep Shah <email address hidden>
Date: Sun Jul 30 20:26:55 2017 -0500

Code changes to address an issue with RD Collision

In large Contrail deployments, compute IP addreses are often reused
across data centers, causing a RD Collision issue, when data centers
are inter-connected through a hierarchical BGP topology.

The implemented solution involves a configurable seeding parameter
at control nodes to make the generated RD unique. Specifically,
the operator configures a 2-byte route_distinguisher_cluster_seed
that is guaranteed to be unique across all managed clusters.

Change-Id: I4154f17cdbb74dc6269b07c265b24580b72d6b96
Closes-Bug: #1679198
Implements: blueprint user-defined-rd-range