Automate icingaweb2 setup

[arjanoosting]

As discussed the code to automate the icingaweb2 setup (Fixes #2)
This is still work in progress...

I introduced quite a lot of new variables and I am not really sure about the naming convention for those yet.

TODO: Also not all the _default and _custom variants are there yet

Also for Icingaweb you always? wan't an Icinga API user. So we maybe might just as well create that one in the default playbook when i2_setup_webui is set?

TODO: The OS user and group of the IcingaWeb configuration should have defaults based on the OS.

I am still figuring out how the other IcingaWeb2 modules need to be installed, probably I also will change some stuff there as well as we will be using the Director and GraphiteWeb modules

[kwisatz]

Thanks, I'll take a look at it. Diffs of this size are easier to digest…

[kwisatz]

Looks good! I'd just wait for you to act on your #TODO items, such as the i2_webui_user.

I'd perhaps just use a regular variable for the api user password now and do the vault stuff in a separate diff/PR?

Also, we already have i2_api_users on the masters (in my case, inside group_vars/masters/basic.yml), shouldn't we try to re-use them?
Well, either that, or as you said, have the config here, but then automatically generate the api user. So that'd mean, e.g. before running the Master - Create Api-Users config file task, merge this user into i2_api_users ?!

[kwisatz]

Your dest below are already absolute.
Now, I might have used dest: "/etc/icingaweb2/{{ item.dest }}" here, but I can also see the advantage of having the absolute path below. I'd still refactor this and move the common root up here.