RETIRED, further work has moved to Debian project infrastructure
f2ba54b62b
A common scenario in database interaction is to check some values in database and update them if some condition is met (or is not met). To prevent race conditions in such scenarios it is recomended to isolate appropriate transactions at read level, so two "select" operations are not executed in parallel. This may be achieved either by modifying transaction_isolation_level or by doing "selects" with a "for update" keyword, which puts a lock on the entries being selected thus blocking any other selects which may run in parallel transaction. The problem is that SELECT FOR UPDATE is not fully supported in Galera clusters which are a common tool for building HA openstack environments. Such statements may have non-determenistic results - see [1] for more details. This patch intoruduces a simple exclusive lock mechanics: it executes a simple insert or update operation into a special table. Any other transactions attempting to do the same will block until the first one completes in one way or another. This results in a simple but reliable locking solution, which may be not as effecient as dedicated distributed lock systems but still do its job nicely. Partial-bug: #1440094 Change-Id: Ib606f33b832b04a3ecac27e1e10018ea8fd503a5 |
||
---|---|---|
contrib | ||
doc/source | ||
etc | ||
functionaltests | ||
meta | ||
murano | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.testr.conf | ||
babel.cfg | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
MANIFEST.in | ||
openstack-common.conf | ||
README.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
Murano
Murano Project introduces an application catalog, which allows application developers and cloud administrators to publish various cloud-ready applications in a browsable categorised catalog, which may be used by the cloud users (including the inexperienced ones) to pick-up the needed applications and services and composes the reliable environments out of them in a "push-the-button" manner.
Project Resources
Project status, bugs, and blueprints are tracked on Launchpad:
Developer documentation can be found here:
Additional resources are linked from the project wiki page:
License
Apache License Version 2.0 http://www.apache.org/licenses/LICENSE-2.0