
A recent change to oslo allows the configuration of the interval that ProcessLauncher waits between checks of child exit. The default interval of 0.01s resulted in the neutron service consuming unnecessary cpu cycles checking whether api workers had exited (5% cpu on idle in a VM). This patch extends the interval to 1s to minimize the cost of the checks. Change-Id: I0407ccb2db65cd3839586faff15e70dbc35f005e Closes-bug: #1095346
# -- 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>.