Hi Darragh,
I'm using Kilo and did not see any traceback with your patch.
I'm using a multi-node setup. So I applied your patch to the Compute node and restarted the q-agt service.
When a VM is launched at the Compute node, the correct MTU 9000 is configured at all interfaces and devices:
1. VM eth0 interface: $ ifconfig eth0 | grep MTU UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1
2. Compute node: localadmin@qa5:/opt/stack/neutron$ brctl show bridge name bridge id STP enabled interfaces brqb5924fb1-0f 8000.6805ca30255b no eth5.300 tap1425c7b3-f2 virbr0 8000.000000000000 yes
localadmin@qa5:/opt/stack/neutron$ ip -o l | cut -d' ' -f2,5 | grep eth5 eth5: 9000 eth5.300@eth5: 9000
localadmin@qa5:/opt/stack/neutron$ ip -o l | cut -d' ' -f2,5 | grep brq brqb5924fb1-0f: 9000
localadmin@qa5:/opt/stack/neutron$ ip -o l | cut -d' ' -f2,5 | grep tap tap1425c7b3-f2: 9000
Hi Darragh,
I'm using Kilo and did not see any traceback with your patch.
I'm using a multi-node setup. So I applied your patch to the Compute node and restarted the q-agt service.
When a VM is launched at the Compute node, the correct MTU 9000 is configured at all interfaces and devices:
1. VM eth0 interface:
$ ifconfig eth0 | grep MTU
UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1
2. Compute node: qa5:/opt/ stack/neutron$ brctl show
tap1425c7b3- f2
localadmin@
bridge name bridge id STP enabled interfaces
brqb5924fb1-0f 8000.6805ca30255b no eth5.300
virbr0 8000.000000000000 yes
localadmin@ qa5:/opt/ stack/neutron$ ip -o l | cut -d' ' -f2,5 | grep eth5
eth5: 9000
eth5.300@eth5: 9000
localadmin@ qa5:/opt/ stack/neutron$ ip -o l | cut -d' ' -f2,5 | grep brq
brqb5924fb1-0f: 9000
localadmin@ qa5:/opt/ stack/neutron$ ip -o l | cut -d' ' -f2,5 | grep tap
tap1425c7b3-f2: 9000