Re: [Openstack-operators] Setting default MTU fro project networks?

2016-11-20 Thread Kevin Benton
Sorry about the delay, a couple of questions. You're not setting network_device_mtu, right? Also, when you see the 1458 MTU, is that in the API response from neutron on a 'neutron net-show', Or is that just what you are seeing in the interfaces on the compute nodes? Setting the following in

Re: [Openstack-operators] Setting default MTU fro project networks?

2016-11-08 Thread Jonathan Proulx
On Mon, Nov 07, 2016 at 02:12:14PM -0800, Kevin Benton wrote: :Which version of Neutron are you on now? Changing the config options had no :impact on existing networks in Mitaka. After updating the config, only new :networks will be affected. You will need to use an SQL query to update the

Re: [Openstack-operators] Setting default MTU fro project networks?

2016-11-07 Thread Kevin Benton
Which version of Neutron are you on now? Changing the config options had no impact on existing networks in Mitaka. After updating the config, only new networks will be affected. You will need to use an SQL query to update the existing network MTUs. This was changed in Newton

[Openstack-operators] Setting default MTU fro project networks?

2016-11-04 Thread Jonathan Proulx
Hi All, So long story short how do I get my ml2/ovs GRE tenant network to default to MTU 9000 in Mitaka - or - get dhcp agents on on netork node to give out different MTUs to different networks? Seems between Kilo (my last release) and Mitaka (my current production world) Neutron got a lot