On Thu, Oct 30, 2014 at 2:28 AM, Robin Lee Powell <
rlpow...@digitalkingdom.org> wrote:
> On Wed, Oct 29, 2014 at 02:09:25AM -0700, Gavin Williams wrote:
> > Sounds like The Foreman [1] might be a good option if you want to manage
> > 'should', not 'is'...
> >
> > [1] http://theforeman.org/
>
> *n
On Wed, Oct 29, 2014 at 02:09:25AM -0700, Gavin Williams wrote:
> Sounds like The Foreman [1] might be a good option if you want to manage
> 'should', not 'is'...
>
> [1] http://theforeman.org/
*nod* Thanks, I should look at that again; it's been a while.
Unfortunately our internal abstractio
Sounds like The Foreman [1] might be a good option if you want to manage
'should', not 'is'...
[1] http://theforeman.org/
On Wednesday, 29 October 2014 03:35:36 UTC, Robin Powell wrote:
>
> On Sun, Oct 26, 2014 at 06:09:08PM -0700, Garrett Honeycutt wrote:
> > On 10/26/14 4:46 PM, Robin Lee Po
On Sun, Oct 26, 2014 at 06:09:08PM -0700, Garrett Honeycutt wrote:
> On 10/26/14 4:46 PM, Robin Lee Powell wrote:
> >
> > So I've been using puppet for a long time, and the one thing
> > I've never solved to my satisfaction is a way to have a single
> > source of truth that acts as both instructio
On 10/26/14 4:46 PM, Robin Lee Powell wrote:
>
> So I've been using puppet for a long time, and the one thing I've
> never solved to my satisfaction is a way to have a single source of
> truth that acts as both instructions to puppet *and* as a system
> inventory that I can use for general opertai
