101bacff26
This updates the mod_wsgi configuration and installation information to be more in line with current usage. It also makes the recommendation to use mod_wsgi more strongly than has been made in the past. In general we don't want people to be running ceilometer-api at all, but it is good for them to have the option. Also an effort has been made to clarify the difference between rpm and deb installations of Apache. DocImpact Change-Id: I11f92d91f4bdea884c266b91b52f9d012abd33b9 Partially-Implements: blueprint remove-web-eventlet
2.3 KiB
Installing the API behind mod_wsgi
Ceilometer comes with a few example files for configuring the API
service to run behind Apache with mod_wsgi.
app.wsgi
The file ceilometer/api/app.wsgi sets up the V2 API WSGI
application. The file is installed with the rest of the ceilometer
application code, and should not need to be modified.
etc/apache2/ceilometer
The etc/apache2/ceilometer file contains example
settings that work with a copy of ceilometer installed via devstack.
../../../etc/apache2/ceilometer
On deb-based systems copy or symlink the file to
/etc/apache2/sites-available. For rpm-based systems the file will go in/etc/httpd/conf.d.Modify the
WSGIDaemonProcessdirective to set theuserandgroupvalues to a appropriate user on your server. In many installationsceilometerwill be correct.Enable the ceilometer site. On deb-based systems:
$ a2ensite ceilometer $ service apache2 reloadOn rpm-based systems:
$ service httpd reload
Limitation
As Ceilometer is using Pecan and Pecan's DebugMiddleware doesn't
support multiple processes, there is no way to set debug mode in the
multiprocessing case. To allow multiple processes the DebugMiddleware
may be turned off by setting pecan_debug to
False in the api section of
ceilometer.conf.
For other WSGI setup you can refer to the pecan deployment documentation. .. _`pecan deployment`: http://pecan.readthedocs.org/en/latest/deployment.html#deployment