as published a few months ago I worked out a dockerized a jenkins farm where both master as slaves are docker containers working together with services like nexus and such. Next to that setup I've dockerized my home setup where services like pi-hole, home-assistant and others are running as docker containers on a thin client I promoted to my home lab.

To have an overview about all those containers and the resources they are consuming I pulled in the git repo of Brian Christner which spins up a whole prometheus stack with some exporters and a grafana instance to visualize …

I do use puppet as our main configuration management tool. Together with puppetdb all our services are automatically configured from bottom to top.

And it rocks, getting automated as much as possible it is like easy as hell to get a server up and running. The only feature it lacked in my opinion is orchestration. I do know about collective which is made for this purpose.

Only it's yet again using an agent which fails from time to time and eating resources which can be avoided. It's the same reason I don't use the puppet agent daemon but trigger puppet …