* if variable to bind an exporter container to a host port is set, have matrix-domain.conf (nginx) support this

* manipulate some variables to account for just port numbers or 0.0.0.0 IPs

* Make sure to use the right variable in the init.yml files

* Update roles/matrix-prometheus-node-exporter/tasks/init.yml

Co-authored-by: Slavi Pantaleev <slavi@devture.com>

* Update roles/matrix-prometheus-postgres-exporter/tasks/init.yml

Co-authored-by: Slavi Pantaleev <slavi@devture.com>

* remove extraneous variables and whitespace

Co-authored-by: Luca Bilke <luca@gmail.com>
Co-authored-by: Slavi Pantaleev <slavi@devture.com>

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1939

People often report and ask about these "failures".
More-so previously, when the `docker kill/rm` output was collected,
but it still happens now when people do `systemctl status
matrix-something` and notice that it says "FAILURE".

Suppressing to avoid further time being wasted on saying "this is
expected".

Reverts b1b4ba501fdfaa, 90c9801c560b6, a3c84f78ca9c65a, ..

I haven't really traced it (yet), but on some servers, I'm observing
`ansible-playbook ... --tags=start` completing very slowly, waiting
to stop services. I can't reproduce this on all Matrix servers I manage.
I suspect that either the systemd version is to blame or that some
specific service is not responding well to some `docker kill/rm` command.

`ExecStop` seems to work great in all cases and it's what we've been
using for a very long time, so I'm reverting to that.

ExecStopPost should allow us to clean up (docker kill + docker rm)
even if the ExecStart (docker run ..) command failed, and not just after
a graceful service stop was initiated.

Source: https://www.freedesktop.org/software/systemd/man/systemd.service.html#ExecStopPost=

Until now, we were leaving services "enabled"
(symlinks in /etc/systemd/system/multi-user.target.wants/).

We clean these up now. Broken symlinks may still exist in older
installations that enabled/disabled services. We're not taking care
to fix these up. It's just a cosmetic defect anyway.

Expected to have regressed after https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1008

This patch comes with its own downsides (as described in the comments
for matrix_prometheus_node_exporter_container_http_host_bind_port),
but at least there's:
- no security issue
- metrics remain readable from matrix-prometheus (even if the network metrics are inaccurate)

A better patch is certainly welcome.

This reverts commit d0cd709c08.

Signed-off-by: Ahmad Haghighi <haghighi@fedoraproject.org>

Same reasoning as in 1cd251ed78

These validation tasks should only run when Prometheus is enabled.

It seems like it doesn't cause any issues for any of these services.

The quotes around "host" for both `--pid` and `--net` were
causing trouble for me:

> docker: --pid: invalid PID mode.

and:

> docker: Error response from daemon: network "host" not found.

I've also changed the `-v` call to `--mount` for consistency with the
rest of the playbook.

By running it in a more privileged container with access to the host network stack and such

Basic system stats, to show stuff the synapse metrics
can't show such as resource usage by bridges, etc

Seems to work fine as well.

This too has only been tested on debian amd64 so far