neutron

History

Ihar Hrachyshka a984f9554c Calculate MTU on every network fetch instead of on create 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		2016-07-20 13:26:50 +02:00
..
alembic_migrations	Calculate MTU on every network fetch instead of on create	2016-07-20 13:26:50 +02:00
models	Make pep8 job great again	2016-06-21 16:23:51 +00:00
README	Support for independent alembic branches in sub-projects	2015-08-12 23:50:58 -04:00
__init__.py	Add function to remove constraints from database	2016-07-12 07:26:18 +00:00
alembic.ini	Ease debugging alembic by passing proper scripts path in alembic.ini	2015-06-22 15:44:55 +02:00
autogen.py	Revert "Support unique labels for alembic branches"	2016-07-06 16:51:04 +00:00
cli.py	Revert "Support unique labels for alembic branches"	2016-07-06 16:51:04 +00:00
connection.py	neutron-db-manage: add has_offline_migrations command	2016-01-22 13:55:40 +00:00

README

See doc/source/devref/alembic_migrations.rst

Rendered at
http://docs.openstack.org/developer/neutron/devref/alembic_migrations.html