• 0 Posts
  • 11 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2023

help-circle


  • Just wiped all my comments a couple hours ago with the help of PowerDeleteSuite. Didn’t quite take the first time, and was surprised that it was a clean sweep the second time. From what I’ve read, I shouldn’t have expected that degree of success.

    Even so, I’ll check back periodically to see whether they’ve been ‘restored’.

    I’ll not contribute to that site any longer. I might still pop on over once in a while, eg, if a web search leads me there. But I’ll be sure to have my adblockers/anti-trackers engaged.







  • It occurred to me that NixOS might have a hard time doing something like this:

    • create a 6 node Docker Swarm cluster, where 3 of the nodes are managers

    I can see NixOS doing a fine job of templating a standard build that includes the Docker engine. But working out which one gets to init the swarm, which ones get to join as managers, which ones get to join as workers? Yeah, that’s probably better off left to something like Ansible.


  • Thanks for this, it was definitely a nice overview. Not the first time I’d heard of NixOS, but I do seem to be seeing more frequent and more substantial discussions of it.

    What I’m getting from all this, is that it looks to be a great way to set up reproducible desktop environments. And servers too, I suppose.

    What I’m not getting from this: a compelling reason to switch from established players like RHEL and Ubuntu in combination with cloud-init and Terraform and the likes of Chef/Puppet/Ansible/Salt to spin up a cluster in the cloud, reconfigure, tear down, etc.

    In case anyone is misreading me: this is not a dig at NixOS. It definitely looks interesting. Like, to the point that I’ll at least spin up a VM on my Manjaro laptop and see whether I should perhaps consider wiping and reinstalling with NixOS. The “configuration through code” is extremely appealing here.

    My concern here is corporate inertia. And before anyone gets gets ready to launch a diatribe about how corporations don’t decide what the best tech is, I will agree with you. I’ve been around a while, and excitedly watched as Unix ramped up and displaced platforms like VAX/VMS and AOS/VS, using smaller and faster hardware. Then along came Linux and the battle for which distros would dominate.

    As for configuration through code, I’ve been keeping a keen eye on things (tinkering when it’s been possible to do so) since the days of cfengine and Jumpstart. I used to share this site with anyone that would listen to me; it’s dated now, but the underlying principles are (were?) solid: http://infrastructures.org/

    So for now, I think I’ll have to limit my professional NixOS usage to tinkering and potentially useful side projects. For personal usage? Yeah, it might become my daily driver, but I need to find the time to tinker.

    I will say that I’m presently involved in an effort to test something out that has my company’s product available using rpm-tree. Not my decision, this is all being driven by a customer that has a lot of clout; they really, really want to use rpm-tree. It’s proven to be a bit onerous at times.

    What this NixOS discussion has managed to do for me is to have me wondering whether a NixOS approach would have worked out better; my sense is that yeah, maybe it would have. But my feelings here might simply be the result of “woo, shiny new object”, which has definitely colored my opinions of things in my career of ~35 years. Something that I’ve had to restrain my excitement over, pending corporate sanity checks.