From owner-freebsd-hackers@FreeBSD.ORG  Mon Nov  4 14:48:10 2013
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id B76BF70F
 for <freebsd-hackers@freebsd.org>; Mon,  4 Nov 2013 14:48:10 +0000 (UTC)
 (envelope-from feld@FreeBSD.org)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com
 [66.111.4.28])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 8AD052A09
 for <freebsd-hackers@freebsd.org>; Mon,  4 Nov 2013 14:48:10 +0000 (UTC)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45])
 by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 22BE12136A
 for <freebsd-hackers@freebsd.org>; Mon,  4 Nov 2013 09:48:07 -0500 (EST)
Received: from web3 ([10.202.2.213])
 by compute5.internal (MEProxy); Mon, 04 Nov 2013 09:48:08 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=
 messagingengine.com; h=message-id:from:to:mime-version
 :content-transfer-encoding:content-type:in-reply-to:references
 :subject:date; s=smtpout; bh=1QcS8bqorT6cMhJSJ4kzo7CAtU0=; b=YRR
 22kjU/z+vXHOq8BfBx9VNAt7q2d0YJ22aslpHYpOwQEYdprSbbGPxMbniARFdmfD
 AuH9RdROTktgn97rryZl97r436blH7L4Jsl7hm1SoGYqVfLqkdK+7AbsvLRP1Al/
 uHJKRn4ydLZw/trooultpzvquWgwQE6hCsjUydPI=
Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99)
 id F3CA810B5A6; Mon,  4 Nov 2013 09:48:06 -0500 (EST)
Message-Id: <1383576486.2000.42722261.6F9C8CF8@webmail.messagingengine.com>
X-Sasl-Enc: plIaqfyi55ae6VdGsNEQa+YCVN6bsp6o/w6tBKY3AxGP 1383576486
From: Mark Felder <feld@FreeBSD.org>
To: freebsd-hackers@freebsd.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
X-Mailer: MessagingEngine.com Webmail Interface - ajax-d4893488
In-Reply-To: <F9A7386EC2A26E4293AF13FABCCB32B3011DC398B5@janus.anserinae.net>
References: <F9A7386EC2A26E4293AF13FABCCB32B3011DC398B5@janus.anserinae.net>
Subject: Re: pkgng for configuration management? 
Date: Mon, 04 Nov 2013 08:48:06 -0600
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Nov 2013 14:48:10 -0000

On Sun, Nov 3, 2013, at 14:49, Kamil Choudhury wrote:
> I've been setting up a private pkgng repository to push software to a
> family of about 20 different hosts. 
> 
> One command software deployment is pretty awesome, so I got to thinking:
> why not go one step further and start pushing configurations for each of
> these hosts via pkgng as well (either by putting the config files into
> the initial software pkg, or via a separate pkg that installs only the
> configurations)? 
> 
> Has anyone else tried going down this rabbit hole? If so, what has your
> experience with the system been?  
> 

I suppose you could create metapackages that write out configuration
files. I'm not sure I like that approach, though. People tend to
gravitate towards things like puppet/chef/ansible/etc.