From owner-freebsd-pkg@FreeBSD.ORG Fri Sep 20 05:58:00 2013 Return-Path: Delivered-To: freebsd-pkg@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id AEB3F88E for ; Fri, 20 Sep 2013 05:58:00 +0000 (UTC) (envelope-from bsd-src@helfman.org) Received: from mail-pb0-f49.google.com (mail-pb0-f49.google.com [209.85.160.49]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 864E12FFB for ; Fri, 20 Sep 2013 05:58:00 +0000 (UTC) Received: by mail-pb0-f49.google.com with SMTP id xb4so9240168pbc.36 for ; Thu, 19 Sep 2013 22:57:54 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=xW2ymkoUaYLN8VkqrxfbSr9K0BdjU2MZeZ2HubA+iaw=; b=SXCR95rOnapP7o0l3ox/H5oPQdhtU6KnJtCRHedUpQC1vplL4+jG40x2AGSCav7oN7 F5sEEOIsby07YriV2ApzqocqfRRl75H8rknpvKvi8cuEaKildMTrVHx6PFqNKUZ2RW6N tmosY5iEWGcDf43qGjWrCVpGCgxjH85J4b9c/F3cJpuDDHGkSIX4b0VqZc+Xdv/+11Kg ND+1yHmdg50gJHb3AAo1v4wK8KfC6sFmylXEU0RVB9rn6+cKiVry98M0MtUGr2DP0hnD BfuxMnZuymASiCUs+PLYtc6mtsbT2anfIDCP/X6DP4gKWCNe3sMXYBEMhQXhw4HmPhmf RPhw== X-Gm-Message-State: ALoCoQlsHd1AOc5X1YLmJ5qOUhVsyFmGrvQimEQEd93WxUsato5hJXs87RFZta1EfNlv7c7yNpqp MIME-Version: 1.0 X-Received: by 10.69.12.36 with SMTP id en4mr6066789pbd.54.1379656267967; Thu, 19 Sep 2013 22:51:07 -0700 (PDT) Sender: bsd-src@helfman.org Received: by 10.70.100.165 with HTTP; Thu, 19 Sep 2013 22:51:07 -0700 (PDT) In-Reply-To: <523B9CAF.5060002@gmail.com> References: <523B9CAF.5060002@gmail.com> Date: Thu, 19 Sep 2013 22:51:07 -0700 X-Google-Sender-Auth: XaiCpglM4xpI78NyLN3OtSJNik4 Message-ID: Subject: Re: pkg integration spacewalk question From: Jason Helfman To: Jason Unovitch Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-pkg@freebsd.org X-BeenThere: freebsd-pkg@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Binary package management and package tools discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Sep 2013 05:58:00 -0000 On Thu, Sep 19, 2013 at 5:54 PM, Jason Unovitch wrote: > Hi Jason, > Some of the functionality looks similar to what is in Puppet. I've been > working on finalizing a "how to" running Puppet open source with its > Dashboard on an Nginx/Ruby on Rails/MariaDB back-end. Unfortunately I > haven't tried any FreeBSD clients yet and only have experience with Linux > clients talking to the Puppet on a FreeBSD server. If the pkg integration > works as well as integration with the Linux package mangers, declaring > having the latest versions of packages would be enough to ensure everything > got updated. With a private pkg repo that gets vetted and updated when > security issues come up I could see this working rather well for ensuring > tight configuration control. Once I get around to testing some FreeBSD > clients I'll see how well pkg integration works out. > > If Puppet doesn't work for you, other options to look into are Cfengine, > Chef, and Salt. I've just stuck with the first tool for the job that I > tried as it worked well. I'd be more than happy to point you to the how to > guide when I'm done as I'm planning on putting it up on the forums for > anybody who can benefit from it. > > Cheers, > Jason Unovitch > Hi Jason. I've run puppet for years, but have never run the 'dashboard,' however I have run it recently taking advantage of 'pkg' repositories. This is a different request, though. This is on-demand. So I check a group of servers. I can work with that group of servers, and proactively see how many packages are out-of-date. I can then select those servers, and upgrade packages of those specific systems. I believe part of this can be done in 'puppet,' but puppet is very good at configuration management, and trigger based actions. I have not found any part of puppet that shows it is a good tool for patch management, or massive pkg deployment/upgrades. I may have missed where you can do this efficiently with puppet. However, I would be happy to discover this, as well :) I've worked slightly with the others you had mentioned, but still am unsure if they are as what I described what I am looking for. Nonetheless, I look forward to reading your forum post. -jgh -- Jason Helfman | FreeBSD Committer jgh@FreeBSD.org | http://people.freebsd.org/~jgh | The Power to Serve