-
Notifications
You must be signed in to change notification settings - Fork 22
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Implement binding strategy in creating and binding lport
- see the guide: ansible/doc/binding-strategy.rst Signed-off-by: Hui Kang <kangh@us.ibm.com>
- Loading branch information
Hui Kang
committed
Aug 26, 2016
1 parent
6b1bcd0
commit aaf7a49
Showing
6 changed files
with
146 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,33 @@ | ||
====================== | ||
Binding Strategy Guide | ||
====================== | ||
|
||
Overview | ||
======== | ||
|
||
In OVN, a logical port can be bind to a local OVS port on any chassis/hypervisor, depending on the VM scheduler (e.g., ``nova-scheduler``). The binding strategy potentially impacts the network performance. That is binding all logical ports in a logical network on a single hypervisor performs differently than distributing the ports on multiple hypervisors. | ||
|
||
The container-based ovn-scale-test deployment allows to configure the binding strategy in creating and binding port rally task. | ||
|
||
|
||
Binding Configuration | ||
===================== | ||
|
||
Use ``networks_per_sandbox`` to control how logical networks and the logical ports are bind to chassis. | ||
|
||
For example, given ``ovn_number_chassis: 10`` (4 emulated chassis) and ``ovn_number_chassis: 10`` (10 logical networks), the binding varies depending on the value of ``networks_per_sandbox``. | ||
|
||
- ``networks_per_sandbox: "10"``: this is the default case. All networks will be evenly distributed to all chassis. | ||
|
||
- ``networks_per_sandbox: "2"``: each chassis has ports belong to two logical networks. In this case, the 10 logical networks are divided into 5 groups, say [n0, n1], [n2, n3], [n4, n5], [n6, n7], [n8, n9]. Then ports in [n0, n1] are bind to chassis 0 and 1, [n2, n3] to chassis 2 and 3, and so forth. As a result, each chassis has two logical network as configured. | ||
|
||
- ``networks_per_sandbox: "1"``: each chassis has ports belong to only one logical network. In this case, the 10 logical network will have a one-to-one mapping to the 10 chassis. Note that this is the extreme case as opposite to ``networks_per_sandbox: "10"``. | ||
|
||
|
||
Constraint | ||
~~~~~~~~~ | ||
|
||
Implementation Detail | ||
===================== | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters