Go to file
Peter Razumovsky 48387e92a0 Fix race condition in reload_on_sighup functional
Race condition appears in next situation:

  1. First thread calls _set_config_value for one section.
  2. Second thread calls _set_config_value for another section.
  3. First thread. Config option value set, calls
     open(self.config_file, 'wb'), which erases all file content.
  4. Second thread. In previous point moment second thread tries to
     set config option value to self.config_file, which is empty (see 3).
     So, NoSectionError exception raised.

This patch adds ten retries for setting option value, if NoSectionError
raised, i.e. try to wait until self.config_file is busy.

Change-Id: Ic54ea287ebe4724511f75d42677cae5dfdec4e57
Closes-bug: #1535766
2016-03-15 17:58:31 +00:00
2016-01-25 10:25:39 +00:00
2012-12-02 17:46:15 +00:00
2012-03-14 09:25:54 +11:00
2015-07-08 09:13:35 -04:00
2015-04-28 16:47:07 -04:00
2015-06-23 08:30:39 +02:00
2015-10-22 10:06:05 +08:00
2015-09-22 10:40:48 +00:00
2016-02-19 18:37:59 +03:00
2016-01-17 05:20:40 +00:00

Heat

Heat is a service to orchestrate multiple composite cloud applications using templates, through both an OpenStack-native REST API and a CloudFormation-compatible Query API.

Why heat? It makes the clouds rise and keeps them there.

Getting Started

If you'd like to run from the master branch, you can clone the git repo:

git clone https://git.openstack.org/openstack/heat

Python client

https://git.openstack.org/cgit/openstack/python-heatclient

References

We have integration with

Description
OpenStack Orchestration (Heat)
Readme 215 MiB
Languages
Python 99.5%
Shell 0.5%