RETIRED, further work has moved to Debian project infrastructure
Go to file
Alexander Tivelkov f2ba54b62b A Galera-compliant database locking solution
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
2015-04-13 13:54:54 +00:00
contrib [devstack] Install Murano as plugin for Horizon 2015-04-08 20:17:54 +03:00
doc/source Merge "Murano documentation update" 2015-04-10 20:13:20 +00:00
etc Update default policy settings 2015-04-09 13:57:34 +00:00
functionaltests Mistral integration functional tests - scripts 2015-02-26 14:50:15 +01:00
meta Adds describe method to Network implementations 2015-04-10 17:55:57 +03:00
murano A Galera-compliant database locking solution 2015-04-13 13:54:54 +00:00
tools Use python from venv for subunit-trace 2015-03-13 08:16:48 +00:00
.coveragerc Added coveragerc 2014-06-22 06:41:49 +04:00
.gitignore Added generated sample config to gitignore 2014-11-29 06:45:49 +03:00
.gitreview Update gitreview to match repo rename 2014-05-23 18:21:12 -04:00
.testr.conf Migrate unit test to testtools 2014-06-04 18:41:07 +04:00
babel.cfg Removed all projects except Glazier Api 2013-04-09 13:25:02 +04:00
CONTRIBUTING.rst Workflow documentation is now in infra-manual 2014-12-05 03:30:45 +00:00
HACKING.rst Added developer documentation 2014-04-21 16:32:28 +04:00
LICENSE Added MANIFEST.in and LICENSE 2013-05-31 16:18:01 +04:00
MANIFEST.in Added DB migrations on Alembic 2014-06-20 18:01:34 +04:00
openstack-common.conf Use oslo.i18n for translation 2015-02-19 18:51:22 +03:00
README.rst Rename muranoapi to murano 2014-05-27 15:14:44 +04:00
requirements.txt Merge "Updated from global requirements" 2015-03-27 10:28:58 +00:00
setup.cfg Use oslo.config generator in murano 2014-11-12 17:09:35 +02:00
setup.py Updated from global requirements 2014-12-14 05:10:49 +03:00
test-requirements.txt Set template for docs 2015-04-08 10:44:24 +00:00
tox.ini Use oslo.i18n for translation 2015-02-19 18:51:22 +03:00

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:

https://launchpad.net/murano

Developer documentation can be found here:

https://murano.readthedocs.org

Additional resources are linked from the project wiki page:

https://wiki.openstack.org/wiki/Murano

License

Apache License Version 2.0 http://www.apache.org/licenses/LICENSE-2.0