commit 463f1cb921d958dc11792514b6f255412d95d6a4
Author: Praveen K V <email address hidden>
Date: Fri Apr 29 15:58:11 2016 +0530
Unify flow-update handling
The current code handles flow-update resulting from add/change for
DBEntries (interface, acl, vn, nh) as different cases. However, there is
only a minor difference between handling based on different DBEntries.
This commit unifies the code to handle DBEntry add/change into two
cases,
- Flows need re-valuation. This is case where we only do
policy-lookup and identify new actions
- Flows needing re-computation. This is case where there is route
change and flow need complete re-valuation due to add/delete of
routes
Additionally, two flags are added in flow to ensure state-compression.
Reviewed: https:/ /review. opencontrail. org/19731 github. org/Juniper/ contrail- controller/ commit/ 463f1cb921d958d c11792514b6f255 412d95d6a4
Committed: http://
Submitter: Zuul
Branch: R3.0
commit 463f1cb921d958d c11792514b6f255 412d95d6a4
Author: Praveen K V <email address hidden>
Date: Fri Apr 29 15:58:11 2016 +0530
Unify flow-update handling
The current code handles flow-update resulting from add/change for
DBEntries (interface, acl, vn, nh) as different cases. However, there is
only a minor difference between handling based on different DBEntries.
This commit unifies the code to handle DBEntry add/change into two
cases,
- Flows need re-valuation. This is case where we only do
policy-lookup and identify new actions
- Flows needing re-computation. This is case where there is route
change and flow need complete re-valuation due to add/delete of
routes
Additionally, two flags are added in flow to ensure state-compression.
Change-Id: Ifeb696d2ab651f 656fbafd45e5e66 a52adb65ade
Partial-Bug: #1568126
Partial-Bug: #1572270
Partial-Bug: #1572471