72ac25c929
Nested transactions have unnecessary overhead of starting new transactions in the database and the only place we need them are where we expect duplicate violations during create/update. This gets rid of them for get_objects and delete_objects so we don't adopt additional unnecessary overhead in OVO adoption. Before this patch, update_port calls were resulting in several independent nested transactions that each require multiple round trips to the database. Change-Id: Icbfe678b6f6ebcdcd7f7ca71f6ac5febb64bdaa3 Partially-Implements: blueprint adopt-oslo-versioned-objects-for-db |
||
---|---|---|
.. | ||
db | ||
extensions | ||
plugins | ||
port | ||
qos | ||
README.rst | ||
__init__.py | ||
address_scope.py | ||
agent.py | ||
auto_allocate.py | ||
base.py | ||
common_types.py | ||
exceptions.py | ||
flavor.py | ||
floatingip.py | ||
ipam.py | ||
l3agent.py | ||
metering.py | ||
network.py | ||
ports.py | ||
provisioning_blocks.py | ||
quota.py | ||
rbac_db.py | ||
router.py | ||
securitygroup.py | ||
servicetype.py | ||
subnet.py | ||
subnetpool.py | ||
tag.py | ||
trunk.py | ||
utils.py |
README.rst
Neutron Objects
Directory
This directory is designed to contain all modules which have objects definitions shipped with core Neutron. The files and directories located inside of this directory should follow the guidelines below.
Structure
The Neutron objects tree should have the following structure:
- The expected directory structure is flat, except for the ML2 plugins. All ML2 plugin objects should fall under the plugins subdirectory (i.e. plugins/ml2/gre_allocation).
- Module names should use singular forms for nouns (network.py, not networks.py).