gvasalt/states/gnuviechadmin/gvaldap.sls

include:
  - gnuviechadmin.base
  - gnuviechadmin.django
  - gnuviechadmin.celery

gvaldap-packages:
  pkg.installed:
    - pkgs:
      - libldap2-dev
      - libsasl2-dev
    - require_in:
      - pkg: gnuviechadmin-packages

base-ldap-objects:
  cmd.script:
    - source: salt://gnuviechadmin/gvaldap/create_base_ldap_objects.sh
    - template: jinja
    - runas: root
    - unless: ldapsearch -Y EXTERNAL -H ldapi:// -b "{{ salt['pillar.get']('gnuviechadmin:ldap_base_dn') }}" "cn={{ salt['pillar.get']('gnuviechadmin:ldap_admin_user') }}" | grep -q numEntries
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-29 18:34:40 +01:00			`include:`
			`- gnuviechadmin.base`
Make gvafile deployment work This commit refactors to gnuviechadmin.base state by moving the Django specific parts into gnuviechadmin.django that is now used by gnuviechadmin.gvaldap and gnuviechadmin.webinterface. The script templates gnuviechadmin/gvafile/run_celery.sh and gnuviechadmin/gvafile/settings.sh have been added. 2016-02-06 14:23:05 +01:00			`- gnuviechadmin.django`
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-29 18:34:40 +01:00			`- gnuviechadmin.celery`

			`gvaldap-packages:`
			`pkg.installed:`
			`- pkgs:`
			`- libldap2-dev`
			`- libsasl2-dev`
			`- require_in:`
			`- pkg: gnuviechadmin-packages`
Synchronize salt configuration with gvaldap 2016-01-31 16:34:53 +01:00
			`base-ldap-objects:`
			`cmd.script:`
			`- source: salt://gnuviechadmin/gvaldap/create_base_ldap_objects.sh`
			`- template: jinja`
Use cmd with runas parameter Replace the deprecated user and group parameters with runas to fix deprecation warnings. 2016-09-24 23:53:49 +02:00			`- runas: root`
Synchronize salt configuration with gvaldap 2016-01-31 16:34:53 +01:00			`- unless: ldapsearch -Y EXTERNAL -H ldapi:// -b "{{ salt['pillar.get']('gnuviechadmin:ldap_base_dn') }}" "cn={{ salt['pillar.get']('gnuviechadmin:ldap_admin_user') }}" \| grep -q numEntries`