Commit graph

8 commits

Author SHA1 Message Date
1bb9742751 Setup initial gvafile pillar and state data 2016-02-06 13:54:57 +01:00
b5e28bf507 Switch result backend to redis
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.
2016-01-31 21:08:32 +01:00
e582e4a6c4 Move host information to pillar data 2016-01-31 21:08:32 +01:00
2ff2a8174c Synchronize salt configuration with gvaldap 2016-01-31 21:08:32 +01:00
8396a0788d Improve salt setup
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
2016-01-31 21:08:32 +01:00
6c9caec8d6 make settings configurable via pillar, default to local 2016-01-31 21:08:32 +01:00
1ae6c1e855 finish vagrant configuration
- ignore collected assets
- setup virtualenv and environment variables
- import additional salt state modules
2016-01-31 21:08:32 +01:00
f5945b9849 add PostgreSQL database and message queues to vagrant box 2016-01-31 21:08:32 +01:00