diff options
| author |   Martin Klozik <martin.klozik@tieto.com> | 2018-05-15 01:42:35 -0700 |
|---|---|---|
| committer | Martin Klozik <martin.klozik@tieto.com> | 2018-05-28 05:48:23 -0700 |
| commit | 63b56ed1d74657129006f066a3f118c4c369d23c (patch) | |
| tree | 33624c57bbf9800668647da82bb9d6edbd1bcd93 /conf/02_vswitch.conf | |
| parent | c79adfe7660ffa43f597af794412c0616a785943 (diff) | |
connections: Introduction of generic API
Redesign of vSwitch and vSwitch controller classes, to use generic
connection methods for configuration of vSwitch. This API
is more generic and vSwitch agnostic, thus deployment scenarios like
P2P, PVP, PVVP (i.e. PVVPx) can be used for all (currently)
supported vSwitches. Usage of new API will simplify an introduction
of new vSwitches in the future.
This patchset introduces following changes:
* OVS: implementation of add_, del_, dump_ connection(s) and their
validation methods
* VPP: bidir parameter removed - it is up to the deployment scenario
implementation to take care about bidirectional connections
* P2P and PXP controllers were updated to use connection methods
instead of flow related methods. Thus standard TCs will support
both OVS and VPP. NOTE, PVPV is not supported for VPP (yet?).
* refactoring of vSwitch interfaces and inherited classes
* VPP step driven TCs were replaced by standard TCs with appropriate
deployment scenarios. This is for backward compatibility with
TC reporting. Once reporting of VPP TC results into results DB will be
modified, this TCs can be removed.
* OVS routing tables support was generalized to support P2P and
PXP deployments and step driven TCs. Usage of OVS routing tables
is now configurable (turned off by default) for better comparison of
results among various vSwitches.
* Multistream pre_installed_flows feature was generalized to
support P2P and PXP deployments and step driven TCs.
* IxNet: TRAFFIC['l4']['dstport'] will be used as a start value for port
iteration if L4 multistream feature is enabled.
* OVS: default flow template is now configurable via OVS_FLOW_TEMPLATE
* OVS: support of TRAFFIC['flow_type']='ip' was generalized to work
with connection methods (i.e. with P2P and PXP deployments and
step driven TCs)
* integration TCs: modification of integration TCs and their macros to
utilize new generic connection based API
* CI: list of TCs for VERIFY & MERGE jobs was changed to run
the same generic tests for both OVS & VPP
* documentation update
* small fixes and improvements
JIRA: VSPERF-579
Change-Id: If4e6e6037929eab9f16c2bbcb8a0fb30e5d6f9b0
Signed-off-by: Martin Klozik <martin.klozik@tieto.com>
Reviewed-by: Richard Elias <richard.elias@tieto.com>
Reviewed-by: Al Morton <acmorton@att.com>
Reviewed-by: Christian Trautman <ctrautma@redhat.com>
Reviewed-by: Sridhar Rao <sridhar.rao@spirent.com>
Diffstat (limited to 'conf/02_vswitch.conf')
| -rw-r--r-- | conf/02_vswitch.conf | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/conf/02_vswitch.conf b/conf/02_vswitch.conf index c9ffa0b7..873b5bca 100644 --- a/conf/02_vswitch.conf +++ b/conf/02_vswitch.conf @@ -210,6 +210,15 @@ OVS_VSCTL_ARGS = [] OVS_OFCTL_ARGS = ['-O', 'OpenFlow13'] # backward compatible default value OVS_APPCTL_ARGS = [] +# default flow template to be used by OVS classes +OVS_FLOW_TEMPLATE = { + 'idle_timeout': '0' +} + +# enable or disable configuration of routing tables; See vswitchperf_design.rst +# for details. +OVS_ROUTING_TABLES = False + ######################### ## VPP ######################### |