respect origin vn attribute if it is more than 8M

Bug #1612415 reported by Nachi Ueno
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R3.1
Fix Committed
Medium
Nischal Sheth
Trunk
Fix Committed
Medium
Nischal Sheth

Bug Description

Respect origin vn attribute if it is more than 8M.

We need to import origin vn attribute when we enable service chaining
between multiple clusters.
Currently, we are ignoring this attribute if the route is coming in eBGP
connection.
In this bug, we amend this process so that we respect the value if it is more than 8M such as we are doing it in security group.

Nischal Sheth (nsheth)
information type: Proprietary → Public
Nischal Sheth (nsheth)
summary: - respect origin vn attribute if it is more than 6M
+ respect origin vn attribute if it is more than 8M
description: updated
Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] master

Review in progress for https://review.opencontrail.org/23229
Submitter: Nischal Sheth (<email address hidden>)

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] R3.1

Review in progress for https://review.opencontrail.org/23230
Submitter: Nischal Sheth (<email address hidden>)

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : A change has been merged

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

commit 82682315c54608c474d7b94f8250890bc970dc82
Author: Nischal Sheth <email address hidden>
Date: Thu Aug 11 14:25:59 2016 -0700

Treat VN index >= 8000000 as global

This is required for correct operation in multi-region scenarios with
service chaining. If there are 2 or more regions re-originating routes
for service chaining, we do not want to derive the origin vn from the
route targets of routes received from other regions. We want the global
controller to manage allocation of vn ids and trust received values if
they have been allocated by global controller.

Values greater than 8000000 are treated as global and are allocated by
the global controller. Need to disregard the ASN and compare only the
vn ids in this case.

Change-Id: I2404517b5d0024ebbea04eb053273aea45ddf20d
Closes-Bug: 1612415

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote :

Reviewed: https://review.opencontrail.org/23230
Committed: http://github.org/Juniper/contrail-controller/commit/115f95887ddd5578da3f7f8708dcb84958686318
Submitter: Zuul
Branch: R3.1

commit 115f95887ddd5578da3f7f8708dcb84958686318
Author: Nischal Sheth <email address hidden>
Date: Thu Aug 11 14:25:59 2016 -0700

Treat VN index >= 8000000 as global

This is required for correct operation in multi-region scenarios with
service chaining. If there are 2 or more regions re-originating routes
for service chaining, we do not want to derive the origin vn from the
route targets of routes received from other regions. We want the global
controller to manage allocation of vn ids and trust received values if
they have been allocated by global controller.

Values greater than 8000000 are treated as global and are allocated by
the global controller. Need to disregard the ASN and compare only the
vn ids in this case.

Change-Id: I2404517b5d0024ebbea04eb053273aea45ddf20d
Closes-Bug: 1612415

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.