- setup listener and pg_hba.conf for PostgreSQL server
- add state code for gva
- add macros for nginx and uwsgi with Python 3 support
- add pillar data for gva
This commit takes care of making rabbitmq and redis work on a messaging
server. The configuration of gvaldap and gvaweb has been adapted to make
both applications work with actual running rabbitmq and redis.
This commit improves the gvaweb celery worker setup based on the work
that has been done for gvaldap before. Old files have been removed and
the setup uses the macros from gnuviechadmin/gvaapp_macros.sls.
The AMQP result backend proved as impractical, this commit switches to
redis instead. The redis server is setup on the webinterface host but
can be configured on another host.
This commit improves the salt setup of the Vagrant box:
- Salt output is reduced to log level warning
- Hosts entries are created for the internal IPs of all planned gva
component VMs
- .bashrc and a .bash_functions sourced from it are now managed for the
vagrant user
- the VM name has been changed to gva.local
- recent salt versions do not depend on m2crypto anymore, therefore it
is now installed before x509certificate functions are called
- the rabbitmq_vhost for gva is now setup before any users are created
because the previous implementation was broken with recent salt
versions
- the gnuviechadmin-locale-data-compile step has been simplified because
Django 1.9's compilemessages takes care of recursive .mo file
compilation
- pillar data has been separated by role (especially queue permissions
and credentials)
- salt configuration is now unified with gvaldap
Jan Dittberner