ECMP load balance parameters can be configured at global, vn and interface level.
Priority (highest to lowest)- Interface, VN, Global.
This config is stored in path. When path is exported to controller, fields in
load-balance-fields are populated using the same. Agent currently provides field
based hashing only. So every controller message will have load-balance-type set
to field-hash. Similarly reflected routes from CN will be used to extract fields
to be used for hashing and populated in respective path.
Agent by default will use all fields.
Reviewed: https:/ /review. opencontrail. org/16283 github. org/Juniper/ contrail- controller/ commit/ f6dd3dc4750ea0f a18c3e0989d7519 de05c19511
Committed: http://
Submitter: Zuul
Branch: master
commit f6dd3dc4750ea0f a18c3e0989d7519 de05c19511
Author: Manish Singh <email address hidden>
Date: Wed Jan 13 16:07:24 2016 +0530
ECMP load balance configuration agent changes.
ECMP load balance parameters can be configured at global, vn and interface level.
Priority (highest to lowest)- Interface, VN, Global.
This config is stored in path. When path is exported to controller, fields in
load-balance-fields are populated using the same. Agent currently provides field
based hashing only. So every controller message will have load-balance-type set
to field-hash. Similarly reflected routes from CN will be used to extract fields
to be used for hashing and populated in respective path.
Agent by default will use all fields.
Closes-bug: 1498765
Conflicts: agent/controlle r/controller_ peer.cc agent/openstack /instance_ service_ server. cc agent/oper/ inet_unicast_ route.cc agent/oper/ metadata_ ip.cc agent/oper/ vm_interface. cc agent/test/ test_util. cc
src/vnsw/
src/vnsw/
src/vnsw/
src/vnsw/
src/vnsw/
src/vnsw/
Change-Id: I652f65b5b6b56f e20e26a0a0bb7cd f6799b98811