3be1d7a75c
The loopingcall thread here was started before processes fork and so the thread stops working after the fork call. This is a problem that will probably need to be worked out in the long run. To ensure that this notifier works correctly in all processes, this change replaces the persistent loopingcall thread with a thread created on demand to delay and batch up notifications. The first notification will trigger spawning the thread to wait to send it. Any notifications that come in the meantime will notice that there is already a thread waiting to send and will return without spawning. Change-Id: I519d4e89b8cee341c0e1cfffbce3e77151e8202a Closes-Bug: #1301035 |
||
---|---|---|
bin | ||
doc | ||
etc | ||
neutron | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.pylintrc | ||
.testr.conf | ||
babel.cfg | ||
HACKING.rst | ||
LICENSE | ||
MANIFEST.in | ||
openstack-common.conf | ||
README.rst | ||
requirements.txt | ||
run_tests.sh | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
TESTING.rst | ||
tox.ini |
# -- Welcome!
You have come across a cloud computing network fabric controller. It has identified itself as "Neutron." It aims to tame your (cloud) networking!
# -- External Resources:
The homepage for Neutron is: http://launchpad.net/neutron . Use this site for asking for help, and filing bugs. Code is available on github at <http://github.com/openstack/neutron>.
The latest and most in-depth documentation on how to use Neutron is available at: <http://docs.openstack.org>. This includes:
Neutron Administrator Guide http://docs.openstack.org/trunk/openstack-network/admin/content/
Neutron API Reference: http://docs.openstack.org/api/openstack-network/2.0/content/
The start of some developer documentation is available at: http://wiki.openstack.org/NeutronDevelopment
For help using or hacking on Neutron, you can send mail to <mailto:openstack-dev@lists.openstack.org>.