Idempotent issues... about ansible-nginx

[drybjed]

I think cleaning up old nginx config files could be added. It would work like this:

• set a delete: True key in server configuration
• rerun the playbook, so that Ansible deletes symlinks to the configs, configs themselves and reloads nginx
• remove the server configuration from inventory

This will allow you do do something like:

nginx_servers: [ '{{ nginx_old_server }}', '{{ nginx_new_server }}' ]

nginx_old_server:
  name: [ 'example.com' ]
  enabled: False
  delete: True

nginx_new_server:
  name: [ 'example.com' ]
  enabled: True

I think this should remain idempotent as well. I will look into it in the near future.

Makes sense to me. Prior to this we were also using Jinja2 templating for our webserver.conf files and then just manually creating the symlink. Your approach works really well but I didn't see a way to trigger options based on a variable. Basically the ability to build something like:

  location ~ ^/.*/_mapping {
    proxy_pass http://127.0.0.1:9200;
    proxy_read_timeout 90;
    {% if kibana_password_protect_all %}
    auth_basic "Restricted";
    auth_basic_user_file /etc/nginx/conf.d/kibana.htpasswd;
    {% endif %}
  }

[drybjed]

nginx_server_kibana:
  location:
    '~ ^/.*/_mapping': |
      proxy_pass http://127.0.0.1:9200;
      proxy_read_timeout 90;
      {% if kibana_password_protect_all %}
      auth_basic "Restricted";
      auth_basic_user_file /etc/nginx/conf.d/kibana.htpasswd;
      {% endif %}

Yes, the text block config style is that simple :-) Here's another example: https://github.com/debops/ansible-phpipam/blob/master/vars/main.yml#L44-L50

[drybjed]

@zahlenofzahlen BTW, we have debops.redis, debops.elasticsearch, I haven't decided yet between fluentd and LogStash, what do you use? Either way, is your Kibana role open source? :-)

I'm using debops.nginx and debops.elasticsearch and just modifying https://github.com/geerlingguy/ansible-role-kibana to work with with it. I put in a few things to specify Kibana version, etc. But that's pretty much it. Unfortunately I don't have any of it open source.

[drybjed]

@zahlenofzahlen Interesting to hear about debops.elasticsearch, can you describe your setup? This role was tested extensively locally, but haven't been tried in a real cluster, we are interested in the results.

Well at this point we are developing small reproducible environments so it's not a true cluster. It's just elasticsearch, kibana, and ElasticHQ. If we get the go ahead I might be able to release a debops playbook for graphite/grafana. I haven't started building that yet. It would have elasticsearch as a dependency. We haven't done any real testing with Elasticsearch and honestly if it's not 100% right that's fine as we can afford some manually tweaking after the fact.

[drybjed]

@zahlenofzahlen Your issues have been fixed by dd113d7 and cd5eb63, cheers. :-)