Make configurations on the Neutron controller for starting the Extreme EFA Mechanism Driver and L3 Service plugin, a journal-based plugin.
extreme_l3_efa_v2plugins use a journaling mechanism,
extreme_efa_v2, along with
openvswitch. In the
/etc/neutron/plugins/ml2/ml2_conf.inifile, add the following lines:
[ml2] mechanism_drivers = openvswitch,extreme_efa_v2,sriovnicswitch
The configurations in the following table also affect the working of the
journaling mechanism, which is configured in
|sync_timeout||Sync thread timeout in seconds or fraction.||10|
|retry_count||Number of times to retry a row before failing.||5|
|maintenance_interval||Journal maintenance operations interval in seconds.||300|
|completed_rows_retention||Time to keep completed rows (in seconds).
For performance reasons, do not change this from the default value (0) which indicates completed rows are not kept.
This value is checked every maintenance_interval by the cleanup thread. To keep completed rows indefinitely, set the value to -1.
|journal_rows_threshold||Maximum number of journal rows allowed. If the number of rows exceeds this threshold, then the efa_health tool shows the status as down.||1000|
|efa_status_interval||Journal EFA reachability check interval in seconds||150|
[DEFAULT] service_plugins = efa_topology_plugin,trunk,segments
[DEFAULT] service_plugins = extreme_l3_efa_v2,efa_topology_plugin,trunk,segments
extreme_l3_efa_v2is an L3 Service plugin and is a replacement for the default L3 Service plugin (called router). Only one of them should be used.
[service_providers] service_provider = L3_ROUTER_NAT:extremev2:networking_extreme.l3.l3_flavor_v2 .ExtremeL3ServiceProviderv2:default
Flavors require the default L3 Service plugin (called
other words, flavors can be used only when the service plugin is
service_plugins = router,efa_topology_plugin,trunk,segments
For more information, see L3 Flavors.