Add Glados instance as part of Fluffy deployment

[kdeme]

Glados is a network health monitoring tool for the Portal Network.

There is a public instance available already: https://glados.ethdevops.io/ . But this uses the Trin client as node to access the network.
I occasionally test this locally with our Fluffy client, but it would be nice to have a long running version of this using fluffy.

Glados exists out of 4 parts (glados-monitor, glados-audit, glados-cartographer and glados-web) + a postgresql server + Portal node (fluffy) + access to a Execution layer JSON-RPC API provider (full node/service).

There exists also a docker-compose to set these up (except for the full node/service): https://github.com/ethereum/glados/blob/master/DOCKER_GUIDE.md
But Fluffy support is still waiting in a PR: ethereum/glados#214

This is not that urgent and more a nice-to-have. It could perhaps also be combined with setting up a Fluffy bridge (which would also require access to a full node), after we refactor/harden our Fluffy bridge.

[kdeme]

It would be good to set this up now, to have a proper public "fluffy view" on the Portal network. I have tested locally latest fluffy + latest glados (through docker-compose) and it all works.

I don't really mind whether it gets set up with the Docker compose setup or some other way, but in case of Docker, here are the docs for the docker-compose deployment: https://github.com/ethereum/glados/blob/master/DOCKER_GUIDE.md

For fluffy to be used in the docker compose, we need to set GLADOS_PORTAL_CLIENT=fluffy.

The Glados web dashboard should be made publicly available.

Considering both fluffy & glados development is not (yet) going through some release cycle, I think it would be best if I can do updates manually ourselves after I've tested some new version locally.

Can somebody of devops look into this? cc @jakubgs @yakimant or @apentori

[jakubgs]

You didn't ping anyone in the original issue, so nobody saw it.

[kdeme]

You didn't ping anyone in the original issue, so nobody saw it.

Yeah, I know, no worries, holiday season was starting and it wasn't an urgent task, + the docker-compose was not adapted for fluffy yet.

Anyway, now the time has come where it is getting more important to have this set up, which is why I added comment + cc

[jakubgs]

@markoburcul you can see context on Portal Bridge setup in this issue:

• Set up a fluffy history bridge #182