From e5cf068ad18d27e989234d10b176061adc997b4c Mon Sep 17 00:00:00 2001 From: Sanjay Upadhyay Date: Fri, 28 Apr 2017 12:46:39 +0530 Subject: Configure mtu value for DPDK port MTU value is already written to ifcfg file if provided on the interface, but for dpdk port, we have to apply this to ovs-vsctl command via ovs_extra. This patch is adding the support to configure the given mtu vlaue to the dpdk port using ovs_extra. implements: blueprint ovs-2-6-features-dpdk Change-Id: Ic01ed8cee2edbd648de0b64dc7f01da80c153d81 --- os_net_config/impl_ifcfg.py | 2 ++ 1 file changed, 2 insertions(+) (limited to 'os_net_config/impl_ifcfg.py') diff --git a/os_net_config/impl_ifcfg.py b/os_net_config/impl_ifcfg.py index 8284ad5..6f35688 100644 --- a/os_net_config/impl_ifcfg.py +++ b/os_net_config/impl_ifcfg.py @@ -299,6 +299,8 @@ class IfcfgNetConfig(os_net_config.NetConfig): data += "DEVICETYPE=ovs\n" data += "TYPE=OVSDPDKPort\n" data += "OVS_BRIDGE=%s\n" % base_opt.bridge_name + if base_opt.mtu: + ovs_extra.append("set Interface $DEVICE mtu_request=$MTU") elif isinstance(base_opt, objects.OvsDpdkBond): ovs_extra.extend(base_opt.ovs_extra) # Referring to bug:1643026, the below commenting of the interfaces, -- cgit 1.2.3-korg