From owner-freebsd-ports@FreeBSD.ORG Wed Jan 31 21:05:32 2007 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DFCEA16A402 for ; Wed, 31 Jan 2007 21:05:32 +0000 (UTC) (envelope-from paul+fbsd@it.ca) Received: from mail2.dm.egate.net (mail2.dm.egate.net [216.235.1.136]) by mx1.freebsd.org (Postfix) with ESMTP id 754A013C481 for ; Wed, 31 Jan 2007 21:05:30 +0000 (UTC) (envelope-from paul+fbsd@it.ca) Received: from mail.it.ca (root@[216.235.7.67]) by mail2.dm.egate.net (8.12.11/8.12.11) with ESMTP id l0VKmotj033969 for ; Wed, 31 Jan 2007 15:48:50 -0500 (EST) Received: from mail.it.ca (paul@mail [216.235.7.67]) by mail.it.ca (8.13.3/8.13.3) with ESMTP id l0VKmnRu014695 for ; Wed, 31 Jan 2007 15:48:49 -0500 (EST) (envelope-from paul+fbsd@it.ca) Received: (from paul@localhost) by mail.it.ca (8.13.3/8.13.3/Submit) id l0VKmnEO014694 for freebsd-ports@freebsd.org; Wed, 31 Jan 2007 15:48:49 -0500 (EST) (envelope-from paul+fbsd@it.ca) X-Authentication-Warning: mail.it.ca: paul set sender to paul+fbsd@it.ca using -f Date: Wed, 31 Jan 2007 15:48:49 -0500 From: Paul Chvostek To: freebsd-ports@freebsd.org Message-ID: <20070131204849.GL95758@it.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.12-2006-07-14 Subject: Package management on many hosts X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2007 21:05:33 -0000 So ... on the topic of large-scale FreeBSD deployment ... How are people handling package version consistency in large groups of servers? If you have a web farm with 10 hosts, plus 3 hosts in a QA farm, and you want to make sure you're using the same version everywhere and upgrading production to the version you tested last week in QA, do you just do it manually, perhaps using portdowngrade on each host, or installing binary packages built on one host? Next, how are people dealing with portaudit info for groups of servers? Is the old standard of a cronjob for daily `portaudit -a` results still the best option? I'm putting together some tools to help with this stuff, but I'd hate to duplicate a perfectly functional wheel. Thanks. -- Paul Chvostek Operations / Abuse / Whatever it.canada, hosting and development http://www.it.ca/