Ansible playbook needs an update

[murgurgula]

[DEPRECATION WARNING]: Instead of sudo/sudo_user, use become/become_user and make sure become_method is 'sudo' (default). This feature will be removed in a future release.

Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.

[DEPRECATION WARNING]: Using bare variables is deprecated. Update your playbooks so that the environment value uses the full variable syntax ('{{postgresql_env}}'). This feature
will be removed in a future release. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.

[arm4b]

Part of: #38

Also FYI current Ansible playbooks are considered as outdated,
see Notice in README.md

Rewrite for new packages is required, some work is done in: #42

[murgurgula]

Sorry for the repetitive ticket. I somehow managed to not see the elefant in the room.

[arm4b]

No problem with that,
something not working is really our fault 🌵

Your contribution via submitting an issue make sense to bring more attention to this (and hopefully add priority for something considered as non priority).

[murgurgula]

It's opensource, it's everyone's fault ^_^ ❤️

However, I would really like to see this updated. I need quick provisioning, so if all stackstorm VM fail in our prod, the oncall person could just launch a script and get them magically up and running as before.
In our setup, StackStorm would handle all the problems before making an escalation to Pager Duty, so if we loose the servers, we're blind. Due to this, we need a strategy to recover fast in case of failure of our StackStorm VMs.

Having a working st2 ansible repo would be a great base for that purpose.

Also, the current st2-ansible does not have the st2web package. It would be usefull to add it.