On Tue, May 08, 2012 at 06:00:07AM -0400, Derek J. Balling wrote:
>
> On May 7, 2012, at 12:47 PM, Christopher Wood wrote:
> > Wrapper script (similar concept for anywhere with a yaml reader):
>
> Still have to *write* the YAML files.
I don't think I've ever actually opened a text editor and wri
Thanks R.I. & Craig Dunn
On 8 May 2012 21:43, R.I.Pienaar wrote:
>
> If you want the same abilities that CSV has then this would be your YAML:
>
> sysadmin: y...@your.com
> nameservers: [1.2.3.4, 2.3.4.5]
>
> just that simple, I think this is much clearer than CSV. If people really
> are
That
- Original Message -
> From: "John Warburton"
> To: puppet-users@googlegroups.com
> Sent: Tuesday, May 8, 2012 12:14:48 PM
> Subject: Re: [Puppet Users] Puppet 3.0 and Hiera
>
>
> On 8 May 2012 20:00, Derek J. Balling < dr...@megacity.org > wrote
Still have to *write* the YAML files.
Oh yeah. This is my big motivator sticking with extlookup and not
converting to Hiera - anyone in the team can do CSV. But YAML is
starting to push well into the dev camp and far away from ops (IMHO)
Unless you're doing rich data types such as hashes,
On 8 May 2012 20:00, Derek J. Balling wrote:
>
> On May 7, 2012, at 12:47 PM, Christopher Wood wrote:
> > Wrapper script (similar concept for anywhere with a yaml reader):
>
> Still have to *write* the YAML files.
>
> Oh yeah. This is my big motivator sticking with extlookup and not
converting to
On May 7, 2012, at 12:47 PM, Christopher Wood wrote:
> Wrapper script (similar concept for anywhere with a yaml reader):
Still have to *write* the YAML files.
> Out of nosiness, how do you handle the edgier cases in your manifests? For
> example, how everything is a standard syslog client, exce
On Mon, May 07, 2012 at 12:26:32PM -0400, Derek J. Balling wrote:
>
> On May 7, 2012, at 11:54 AM, Nigel Kersten wrote:
> > Yes. If you're not planning to externalize data at all, the only difference
> > you'll see is that you'll now have Hiera installed on your system when you
> > install Puppe
On Mon, May 7, 2012 at 9:26 AM, Derek J. Balling wrote:
>
> On May 7, 2012, at 11:54 AM, Nigel Kersten wrote:
> > Yes. If you're not planning to externalize data at all, the only
> difference you'll see is that you'll now have Hiera installed on your
> system when you install Puppet 3.0.
>
> Cool
On May 7, 2012, at 11:54 AM, Nigel Kersten wrote:
> Yes. If you're not planning to externalize data at all, the only difference
> you'll see is that you'll now have Hiera installed on your system when you
> install Puppet 3.0.
Cool. Was really panicking there for a moment.
I kinda like having
On Mon, May 7, 2012 at 7:22 AM, Derek J. Balling wrote:
>
> On May 3, 2012, at 1:05 PM, Pieter van de Bruggen wrote:
>
> As many of you may be aware, Hiera will be tightly integrated into Puppet
> in the upcoming release of Puppet 3.0.
>
> What will this mean for sites that have specifically avoi
On May 3, 2012, at 1:05 PM, Pieter van de Bruggen wrote:
> As many of you may be aware, Hiera will be tightly integrated into Puppet in
> the upcoming release of Puppet 3.0.
>
What will this mean for sites that have specifically avoided using Hiera? I
would presume that this should just mean "b
On Sat, May 5, 2012 at 9:26 AM, Trevor Vaughan wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> With the integration of Hiera, is the extlookup functionality being
> deprecated?
>
> If so, I would like to ask that the team add a Hiera backend for the
> existing extlookup data sources.
On 5 May 2012, at 17:26, Trevor Vaughan wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> With the integration of Hiera, is the extlookup functionality being
> deprecated?
>
> If so, I would like to ask that the team add a Hiera backend for the existing
> extlookup data sources.
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
With the integration of Hiera, is the extlookup functionality being deprecated?
If so, I would like to ask that the team add a Hiera backend for the existing
extlookup data sources.
I know that it won't support hashes but it would help to break the
On Fri, May 4, 2012 at 12:05 PM, Ohad Levy wrote:
> On Fri, May 4, 2012 at 12:05 PM, R.I.Pienaar wrote:
>> - Original Message -
>> > From: "Pieter van de Bruggen"
>>
>>
>>
>> >
>> > * How should we integrate hiera_array() and hiera_hash() ?
>> > * How should we integrate hiera ’
On Fri, May 4, 2012 at 12:05 PM, R.I.Pienaar wrote:
>
>
> - Original Message -
> > From: "Pieter van de Bruggen"
>
>
>
> >
> > * How should we integrate hiera_array() and hiera_hash() ?
> > * How should we integrate hiera ’s “default” and “override”
> > parameters?
> > *
On Fri, May 4, 2012 at 5:05 AM, R.I.Pienaar wrote:
>
> I think the plan was that there would be a priority order as below:
>
> - someone wrote in a manifest: class{"foo": something => something}
> - an ENC supplied the values for something on the class foo
> - someone did "include foo" or clas
- Original Message -
> From: "Pieter van de Bruggen"
>
> * How should we integrate hiera_array() and hiera_hash() ?
> * How should we integrate hiera ’s “default” and “override”
> parameters?
> * How should we handle overlaps between data supplied by Hiera
> and d
All sounds very good...
Here’s what’s new:
* Hiera data keys can be namespaced
o (e.g. 'dns::nameserver': '8.8.8.8')
Namespace scoping is defiantly a massive improvement to Hiera - Im
curious how this affects back ends though... Will lookup("nameserver")
called from Puppet in a cla
Greetings,
As many of you may be aware, Hiera will be tightly integrated into Puppet
in the upcoming release of Puppet 3.0. As a final sanity check of this
work, I’d like to open our current plan for integration up for feedback.
This is particularly for feedback from existing Hiera users, but I ho
20 matches
Mail list logo
