| 1 |
--- |
| 2 |
prelude: > |
| 3 |
The ML2 plug-in supports calculating the MTU for networks |
| 4 |
that are realized as flat or VLAN networks, by consulting the |
| 5 |
'segment_mtu' option. Prior to Mitaka, 'segment_mtu' defaults to 0 which |
| 6 |
disables this feature. This creates slightly confusing API results when |
| 7 |
querying Neutron networks, since the plugins that support the MTU API |
| 8 |
extension would return networks with the MTU equal to zero. Networks |
| 9 |
with an MTU of zero make little sense, since nothing could ever be transmitted. |
| 10 |
In Mitaka, 'segment_mtu' now defaults to 1500 which is the standard MTU for Ethernet |
| 11 |
networks in order to improve the "out of box" experience for typical deployments. |
| 12 |
features: |
| 13 |
- In Mitaka, queries to the Networking API for network objects will now |
| 14 |
return network objects that contain a sane MTU value. |
| 15 |
upgrade: |
| 16 |
- Operators using the ML2 plug-in with existing data may need |
| 17 |
to perform a database migration to update the MTU for existing networks |