Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #268962

Re: Current best practices for system configuration management?

From Dan Ritter <dsr@randomstring.org>
Newsgroups linux.debian.user
Subject Re: Current best practices for system configuration management?
Date 2024-04-19 03:00 +0200
Message-ID <IuKLE-7fJ8-7@gated-at.bofh.it> (permalink)
References <IuKiC-7fyI-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Mike Castle wrote: 
> and so on, it is time to explore solutions.  I only have four systems
> at the moment (two physical and two virtual), so I don't think I need
> something too fancy.
> 
> My first thought was to simply add a `Files:` section to *.control
> files I use for my metapackages.  After all, for configs going into
> *.d directories, they are usually easy to just drop in and remove, no
> editing in place required.  But, that is when I discovered that all
> files under `/etc` are treated specially.
> 
> I've found a lot of documentation out there, but, of course, much of
> it is out of date.  https://wiki.debian.org/ConfigPackages , for
> example, seems to recommend slightly old to really old tools.  Tools
> like `ansible`, `puppet` and so on seem, at first blush, aimed at
> larger installations than mine.  But maybe other's experience with
> them will show they scale down fine?
> 
> Anyway, suggestions based upon actually experience would be appreciated.

Chef or Puppet are good, but probably not worth the bother for
4-5 systems. Definitely worthwhile for 10+ systems, and scalable
to thousands. https://cinc.sh is producing a fully open release
of Chef (with the new name, Cinc is not chef). I use Chef at
work.

The easy end of single-machine is etckeeper, which just checks
your /etc (and whatever else you specify) into a local git. The
high end of single machine is Nix, which has a complete language
designed to capture the complete configuration of a system (and
has spawned NixOS, a complete distribution).

The easy end of multi-machine systems is cdist and itamae. You might be
quite happy with those, and itamae is reputedly very Chef-like.


-dsr-

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Current best practices for system configuration management? Mike Castle <dalgoda@gmail.com> - 2024-04-19 02:30 +0200
  Re: Current best practices for system configuration management? Dan Ritter <dsr@randomstring.org> - 2024-04-19 03:00 +0200
    Re: Current best practices for system configuration management? Alexandre Rossi <niol@zincube.net> - 2024-04-19 08:40 +0200
  Re: Current best practices for system configuration          management? Linux-Fan <Ma_Sys.ma@web.de> - 2024-04-19 17:30 +0200
  Re: Current best practices for system configuration management? Andy Smith <andy@strugglers.net> - 2024-04-19 22:50 +0200
  Re: Current best practices for system configuration management? Mike Castle <dalgoda@gmail.com> - 2024-04-21 02:00 +0200
    Re: Current best practices for system configuration management? John Crawley <john@bunsenlabs.org> - 2024-04-21 03:20 +0200
    Re: Current best practices for system configuration management? Mike Castle <dalgoda@gmail.com> - 2024-04-21 04:10 +0200
      Re: Current best practices for system configuration          management? Linux-Fan <Ma_Sys.ma@web.de> - 2024-04-24 18:30 +0200
    Mesh VPN on Debian (Was Re: Current best practices for system  configuration management?) Andy Smith <andy@strugglers.net> - 2024-04-21 15:40 +0200
    Re: Current best practices for system configuration management? Mike Castle <dalgoda@gmail.com> - 2024-05-27 18:40 +0200
  Re: Current best practices for system configuration management? Tim Woodall <debianuser@woodall.me.uk> - 2024-04-21 11:30 +0200

csiph-web