hey Konstantin Boudnik no need to swear. This is not systemd fault, it's our fault, or more like the way we use puppet
On one side we have to target bare metal /vm and on the other side we need to adress more like a microservices setup.
On the bare metal /vm side we have to handle the systemd , in docker we do not have an init system, we are faking it.
Using puppet as an abstraction for both will not work here, since it has to handle services very differently, but puppet has no clue how.
Either implement an abstraction to handle both cases or implement both.
I am thinking about this problem for quite a bit. Since I am now more comfortable with docker I am thinking about to throw away the bare metal support / systemd /sysv init.d support completly and only support microservices within containers for all our components.
That would make render rebuilding of all our packages in whatever distro alot easier ... and we could use docker-swarm or kubernetes to boot up a smoke test environment out of the box.
That way we are parting from the traditional hadoop setups, but it will make our work alot more comfortable.
Surely this sounds like bigtop-2.0 ... but that's definetly the direction I see the most promising solution to some of our problems.