397eb2a2fe
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 |
||
---|---|---|
.. | ||
alembic_migrations | ||
models | ||
README | ||
__init__.py | ||
alembic.ini | ||
autogen.py | ||
cli.py | ||
connection.py |
README
See doc/source/contributor/alembic_migrations.rst Rendered at https://docs.openstack.org/neutron/latest/contributor/alembic_migrations.html