From owner-freebsd-stable@FreeBSD.ORG Thu Feb 5 15:53:08 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 61A769C5 for ; Thu, 5 Feb 2015 15:53:08 +0000 (UTC) Received: from mail0.byshenk.net (portland1.byshenk.net [69.168.54.16]) by mx1.freebsd.org (Postfix) with ESMTP id 3BE9CEBE for ; Thu, 5 Feb 2015 15:53:08 +0000 (UTC) Received: by mail0.byshenk.net (Postfix, from userid 1002) id 010433E8FD; Thu, 5 Feb 2015 07:47:43 -0800 (PST) Date: Thu, 5 Feb 2015 07:47:43 -0800 From: Greg Byshenk To: freebsd-stable@freebsd.org Subject: Re: push a few config files to dozen or so servers Message-ID: <20150205154743.GO88387@mail0.byshenk.net> References: <20150205130234.3fcbabfb@efreet.mimar.rs> <54D37932.7010808@madpilot.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <54D37932.7010808@madpilot.net> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Feb 2015 15:53:08 -0000 On Thu, Feb 05, 2015 at 03:07:46PM +0100, Guido Falsi wrote: > On 02/05/15 13:20, Ronald Klop wrote: > > On Thu, 05 Feb 2015 13:02:34 +0100, Marko Cupa?? > >> thanks to virtualization, my fleet of FreeBSD hosts have grown to more > >> than dozen, and it still grows. There are some files that need to be > >> identical on all of them (aliases, sudoers, root crontab, pkg repo > >> files etc.). > >> > >> I was looking at puppet and cfengine but learning and implementing those > >> seem like an overkill for my purpose. > >> > >> Are there any other elegant solutions which can help me achieve my goal? > > > > Cron and rsync. > > Or create a pkg which you install on all servers. > > He could also use an VCS system (subversion, git, fossil, whatever) and > some scripts. > > This adds the advantage of having history. If it's really limited, you should be able to wrap svn/git and scp/rsync in python/bash/ and have something that works. > > Just some quick ideas. In the end you just want to use something like > > puppet. :-) > > I Agree, in the end that kind of solution is definitely more robust. But, agreeing here, as well, there are some real advantages in ensuring consistency, etc. with something like puppet. And a basic, minimalist puppet is pretty basic and minimal. Puppet can get very complex, but that comes from managing complex environments. -- greg byshenk - gbyshenk@byshenk.net - Portland, OR USA