In addition, the port of zun-api is inconsistent. The devstack script used 9517 and others used 9512. This commit changed to port 9517 in everywhere. Implements: blueprint deploy-zun-api-in-wsgi Change-Id: I08818e417945338d5de5de473f8adc9bf9d63bdc
1.9 KiB
Installing the API behind mod_wsgi
Zun comes with a few example files for configuring the API service to
run behind Apache with mod_wsgi
.
app.wsgi
The file zun/api/app.wsgi
sets up the V2 API WSGI
application. The file is installed with the rest of the zun application
code, and should not need to be modified.
etc/apache2/zun.conf
The etc/apache2/zun.conf
file contains example settings
that work with a copy of zun installed via devstack.
../../../etc/apache2/zun.conf
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
WSGIDaemonProcess
directive to set theuser
andgroup
values to an appropriate user on your server. In many installationszun
will be correct. Modify theWSGIScriptAlias
directive to set the path of the wsgi script. If you are using devstack, the value should be/opt/stack/zun/zun/api/app.wsgi
. In theErrorLog
andCustomLog
directives, replace%APACHE_NAME%
withapache2
.Enable the zun site. On deb-based systems:
$ a2ensite zun $ service apache2 reload
On rpm-based systems:
$ service httpd reload