neutron/neutron/db/migration
Rodolfo Alonso Hernandez 397eb2a2fe Serialize subnet creating depending on the network ID
Add a new DB table "network_subnet_lock". The primary key will be the
network_id. When a subnet is created, inside the write context during
the "subnet" object creation, a register in the mentioned table is
created or updated. This will enforce the serialization of the "subnet"
registers belonging to the same network, due to the write lock in the
DB.

This will solve the problem of attending several "subnet" creation
requests, described in the related bug. If several subnets with the
same CIDR are processed in parallel, the implemented logic won't reject
them because any of them will not contain the information of each other.

This DB lock will also work in case of distributed servers because the
lock is not enforced in the server logic but in the DB backend.

Change-Id: Iecbb096e0b7e080a3e0299ea340f8b03e87ddfd2
Closes-Bug: #1852777
2019-12-02 17:19:03 +00:00
..
alembic_migrations Serialize subnet creating depending on the network ID 2019-12-02 17:19:03 +00:00
models Merge "Relocate Agent DB model" 2016-10-10 16:33:55 +00:00
README Update the documentation link for doc migration 2017-07-22 18:46:13 +09:00
__init__.py Open Ussuri DB branch 2019-08-15 16:30:52 -04:00
alembic.ini Ease debugging alembic by passing proper scripts path in alembic.ini 2015-06-22 15:44:55 +02:00
autogen.py Fix flake8 N534 untranslated exception message 2018-10-19 15:46:04 -04:00
cli.py Open Ussuri DB branch 2019-08-15 16:30:52 -04:00
connection.py neutron-db-manage: add has_offline_migrations command 2016-01-22 13:55:40 +00:00

README

See doc/source/contributor/alembic_migrations.rst

Rendered at
https://docs.openstack.org/neutron/latest/contributor/alembic_migrations.html