a984f9554c
Today, existing networks may not reflect MTU configured for
neutron-server, if they were created when neutron-server was using
different MTU setup for its infrastructure, or when it was using bad
default values for network MTUs (specifically, before Mitaka, all networks
were getting MTU = 0 by default, disabling both advertisement and data
path MTU size enforcement).
This patch stops persisting MTU in the database on network create and
instead calculate it on every network resource fetch.
DocImpact Now changes to MTU configuration options immediately affect
existing network MTUs, not just new networks.
UpgradeImpact Existing networks with invalid MTU persisted in database
may change their MTU values to reflect configuration.
Change-Id: Iee4f5037bf10b73ba98464143b183aacb59c22f2
Closes-Bug: #1556182
13 lines
601 B
YAML
13 lines
601 B
YAML
---
|
|
features:
|
|
- net-mtu extension now recalculates network MTU on each network access, not
|
|
just on creation. It now allows operators to tweak MTU related
|
|
configuration options and see them applied to all network resources right
|
|
after controller restart, both old and new.
|
|
upgrade:
|
|
- Existing networks with MTU values that don't reflect configuration
|
|
will receive new MTU values after controller upgrade. Note that to
|
|
propagate new correct MTU values to your backend, you may need to resync
|
|
all agents that set up ports, as well as re-attach VIFs to affected
|
|
instances.
|