3d669cbd0e
This change to the WSGI code uses openstack.common.service to create multiple worker processes to handle API load. The main process will start up a configurable (workers=??) number of child processes which will all listen on the bind port. The main process becomes the parent and manages the children. The parent is not a worker. Backwards compatibility is preserved by setting api_workers to 0, the default. In this case, no separate worker processes are spawned and the worker threads run in the main process. Implement blueprint multi-workers-for-api-server Change-Id: Iffa76041d0055840ccca852814b0e71f17a950ac
# -- 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>.