5216b02904
We are seeing in the static.openstack.org logs the problem metioned in [1] which is leadning to dropped connections. This mpm showed some scalability bottlenecks in the past leading to the following error: "scoreboard is full, not at MaxRequestWorkers". ... From 2.4.24 onward, mpm-event is smarter and it is able to handle graceful terminations in a much better way I don't think we want to go outside the packages provided by Trusty, and it seems that even upping the number of servers/threads is not a reliable work-around to this problem. It seems like the simplest thing to do is avoid the problem all together by switching to the woker MPM, which is very simliar but not optimised for HTTP keep-alive. Since this is not an ajax-y type interactive server with a lot of long-lived clients, I think this will work fine. [1] https://httpd.apache.org/docs/2.4/mod/event.html Change-Id: I064b81076bcfcb200e0990627fc1aa0be8bbf058
Puppet Modules
These are a set of puppet manifests and modules that are currently being used to manage the OpenStack Project infrastructure.
The main entry point is in manifests/site.pp.
In general, most of the modules here are designed to be able to be run either in agent or apply mode.
These puppet modules require puppet 2.7 or greater. Additionally, the site.pp manifest assumes the existence of hiera.
See http://docs.openstack.org/infra/system-config for more information.
Documentation
The documentation presented at http://docs.openstack.org/infra/system-config comes from git://git.openstack.org/openstack-infra/system-config repo's docs/source. To build the documentation use
$ tox -evenv python setup.py build_sphinx