It's still a fascinating prospect.

I've been toying with the idea of NixOS-as-MDM for some time now. It just occurred to me as I was brushing my teeth that most MDM solutions require a central server (if not all) and that can get expensive and inconvenient. Decentralizing the entire thing makes it more portable, flexible, and frankly, way cooler.

I was thinking of a guy who installed some distributed-computation software on all his school's computers, so he could build an entire Gentoo system, DE and all, in ninety seconds flat (not counting transfer times). Then it occurred to me that if all those machines were the same architecture, there's no reason those compiled objects could not be reused with the exact same optimizations. And since there's already no "central server" (because all of them are servers), you could unify this entire mess into a NixOS config, and you've got yourself a hype train straight out of 2014.

I need sleep.

In reply to @k900:0upti.me
Without effectively rewriting Hydra entirely

In reply to @mrtrk:matrix.org
Has anyone ever tried to deploy all the hydra components separately? from what I understood hydra architecture is meant to be distributed and use postgresql as a message bus

In reply to @janne.hess:helsinki-systems.de
That's mostly true but I think (although I am not sure) that the queue runner expects the drvs from the evaluator in its store

In reply to @casey:hubns.net
the key part there is that the build was cached from another build. you'll need to grab the build info from that original build.