692653f49f
Since the ovs_idl backend maintains an in-memory copy of the DB, read-only commands can be executed w/o creating a transaction. Since it is possible for a function that calls execute() to be automatically nested into an existing transaction, execute() wasn't able to access the result since it only happens once the parent transaction completed. Handling these read-only commands w/o creating a transaction allows the results to be read and avoids wasting resources by creating needless transactions. ReadOnlyCommands can still be used in with transaction(): blocks with no changes. Change-Id: I62d6fc2a209535227686a2397b8f7cb169e7d35b Closes-bug: 1813213 |
||
---|---|---|
doc/source | ||
ovsdbapp | ||
releasenotes | ||
tools | ||
zuul.d | ||
.gitignore | ||
.gitreview | ||
.pylintrc | ||
.stestr.conf | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
README.rst | ||
TESTING.rst | ||
babel.cfg | ||
bindep.txt | ||
lower-constraints.txt | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
ovsdbapp
A library for creating OVSDB applications
The ovdsbapp library is useful for creating applications that communicate via Open_vSwitch's OVSDB protocol (https://tools.ietf.org/html/rfc7047). It wraps the Python 'ovs' and adds an event loop and friendly transactions.
- Free software: Apache license
- Source: http://git.openstack.org/cgit/openstack/ovsdbapp
- Bugs: http://bugs.launchpad.net/ovsdbapp
Features
- An thread-based event loop for using ovs.db.Idl
- Transaction support
- Native OVSDB communication