f971e5d1a4
This patch is changing the commit_block() from the Transaction class to
handle the NOT_LOCKED status and treat it as an error.
The reason to treat it as an error is because, when the connection with
the OVSDB is reestabilished we don't know if that transaction will
belong to a worker that is holding a valid lock or not, so we won't
attempt to retry it.
The patch is also adding a log for unknown status, in case another
status that is not handled by ovsdbapp is returned the log will give us
some hints about what's going on instead of failing siently.
Related-Bug: #1754291
Change-Id: I5dcb226c387092cba1adb9dbf1ec782e0bac66ba
(cherry picked from commit
|
||
---|---|---|
doc/source | ||
ovsdbapp | ||
releasenotes | ||
tools | ||
.gitignore | ||
.gitreview | ||
.pylintrc | ||
.testr.conf | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
README.rst | ||
TESTING.rst | ||
babel.cfg | ||
bindep.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