Re: [Puppet Users] extlookup can't match key.

On Tue, Mar 20, 2012 at 9:55 AM, Nan Liu wrote: > On Tue, Mar 20, 2012 at 9:33 AM, Douglas Garstang > wrote: >> On Tue, Mar 20, 2012 at 8:03 AM, Douglas Garstang >> wrote: >>> On Tue, Mar 20, 2012 at 7:33 AM, Douglas Garstang >>> wrote: On Mon, Mar 19, 2012 at 5:53 PM, Gary Larizza wrote:

Re: [Puppet Users] extlookup can't match key.

On Tue, Mar 20, 2012 at 9:33 AM, Douglas Garstang wrote: > On Tue, Mar 20, 2012 at 8:03 AM, Douglas Garstang > wrote: >> On Tue, Mar 20, 2012 at 7:33 AM, Douglas Garstang >> wrote: >>> On Mon, Mar 19, 2012 at 5:53 PM, Gary Larizza wrote: On Tue, Mar 20, 2012 at 11:35 AM, Douglas

Re: [Puppet Users] extlookup can't match key.

On Tue, Mar 20, 2012 at 8:03 AM, Douglas Garstang wrote: > On Tue, Mar 20, 2012 at 7:33 AM, Douglas Garstang > wrote: >> On Mon, Mar 19, 2012 at 5:53 PM, Gary Larizza wrote: >>> >>> >>> On Tue, Mar 20, 2012 at 11:35 AM, Douglas Garstang >>> wrote: I have a 2.7.6 server and a 2.6.4 cli

Re: [Puppet Users] extlookup can't match key.

On Tue, Mar 20, 2012 at 7:33 AM, Douglas Garstang wrote: > On Mon, Mar 19, 2012 at 5:53 PM, Gary Larizza wrote: >> >> >> On Tue, Mar 20, 2012 at 11:35 AM, Douglas Garstang >> wrote: >>> >>> I have a 2.7.6 server and a 2.6.4 client. I'm trying to use ext_lookup. >>> >>> site.pp: >>> $extlookup_da

Re: [Puppet Users] extlookup can't match key.

On Mon, Mar 19, 2012 at 5:53 PM, Gary Larizza wrote: > > > On Tue, Mar 20, 2012 at 11:35 AM, Douglas Garstang > wrote: >> >> I have a 2.7.6 server and a 2.6.4 client. I'm trying to use ext_lookup. >> >> site.pp: >> $extlookup_datadir = "/etc/puppet/manifests/extdata" >> $extlookup_precedence = ["

Re: [Puppet Users] extlookup can't match key.

On Tue, Mar 20, 2012 at 11:35 AM, Douglas Garstang wrote: > I have a 2.7.6 server and a 2.6.4 client. I'm trying to use ext_lookup. > > site.pp: > $extlookup_datadir = "/etc/puppet/manifests/extdata" > $extlookup_precedence = ["%{fqdn}", "domain_%{domain}", "common"] > Try using Puppet variables:

[Puppet Users] extlookup can't match key.

I have a 2.7.6 server and a 2.6.4 client. I'm trying to use ext_lookup. site.pp: $extlookup_datadir = "/etc/puppet/manifests/extdata" $extlookup_precedence = ["%{fqdn}", "domain_%{domain}", "common"] /etc/puppet/manifests/extdata/common.csv: key1,var1: manifest has: $var1 = extlookup(“key1”, "Un

Re: [Puppet Users] Extlookup and undefined labels.

On Dec 18, 2011, at 6:06 PM, Trevor Vaughan wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > The problem with this is that, should someone forget that default in the > 'defaults' file (or wherever), then the entire manifest explodes over an > entry that I don't care about unless it e

Re: [Puppet Users] Extlookup and undefined labels.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The problem with this is that, should someone forget that default in the 'defaults' file (or wherever), then the entire manifest explodes over an entry that I don't care about unless it exists. Basically, I want some logic to say: *If* we have extloo

Re: [Puppet Users] Extlookup and undefined labels.

- Original Message - > So, I tried to use extlookup and ended up with a typo that made my > configuration explode with a missing label error. > > So, how would one go about making a label optional? As in, try to > look > it up, but I don't really care if you fail as I'll just do somethin

[Puppet Users] Extlookup and undefined labels.

So, I tried to use extlookup and ended up with a typo that made my configuration explode with a missing label error. So, how would one go about making a label optional? As in, try to look it up, but I don't really care if you fail as I'll just do something else. Thanks, Trevor -- Trevor Vaugha

Re: [Puppet Users] extlookup not working correctly in 2.7.6

- Original Message - > I'm trying to upgrade from 2.6.7 to to 2.7.6 and I'm running into an > issue in my extlookup() calls. A lot of the variables which should > be > defined aren't defined within extlookup.rb. I've tested 2.6.7 agent > and 2.7.5 agent against the 2.6.7 master and 2.7.

[Puppet Users] extlookup not working correctly in 2.7.6

I'm trying to upgrade from 2.6.7 to to 2.7.6 and I'm running into an issue in my extlookup() calls. A lot of the variables which should be defined aren't defined within extlookup.rb. I've tested 2.6.7 agent and 2.7.5 agent against the 2.6.7 master and 2.7.6 master. I adjusted extlookup.rb slight

[Puppet Users] extlookup()

Taking a brief look at extlookup() We have a module to setup resolv.conf based on location so we have a % {domain}.csv file more /etc/puppetlabs/puppet/envs/legacy/extdata/ldt.csv domainname,my.domain.com resolvers,10.10.10.10 10.10.10.11 searchpath,sub.my.domain.com sub2.my.domain.com class re

Re: [Puppet Users] Extlookup() again.

My own post? y? On Wed, Aug 3, 2011 at 4:40 PM, Scott Smith wrote: > http://groups.google.com/group/puppet-users/msg/6432a6dd539b542f > > > On Wed, Aug 3, 2011 at 4:37 PM, Douglas Garstang > wrote: > >> Ok, so am I getting 'DougBobBill' when I use $test_var = >> extlookup('testkey', '---',

Re: [Puppet Users] Extlookup() again.

http://groups.google.com/group/puppet-users/msg/6432a6dd539b542f On Wed, Aug 3, 2011 at 4:37 PM, Douglas Garstang wrote: > Ok, so am I getting 'DougBobBill' when I use $test_var = > extlookup('testkey', '---', 'settings') on this file? > > --- > testkey: > - Doug > - Bob > - Bill > > Doug > > On

Re: [Puppet Users] Extlookup() again.

- Original Message - > Ok, so am I getting 'DougBobBill' when I use $test_var = > extlookup('testkey', '---', 'settings') on this file? how are you examining this value? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this

Re: [Puppet Users] Extlookup() again.

Ok, so am I getting 'DougBobBill' when I use $test_var = extlookup('testkey', '---', 'settings') on this file? --- testkey: - Doug - Bob - Bill Doug On Wed, Aug 3, 2011 at 4:34 PM, Aaron Grewell wrote: > It's an array, which can then be exploded into a whole set of package > resources with a si

Re: [Puppet Users] Extlookup() again.

It's an array, which can then be exploded into a whole set of package resources with a single entry: package {$default_packages:} On Wed, Aug 3, 2011 at 4:31 PM, Douglas Garstang wrote: > On Wed, Aug 3, 2011 at 4:25 PM, Aaron Grewell wrote: > >> Example Config: >> --- >> :parser: YAML >> :precede

Re: [Puppet Users] Extlookup() again.

On Wed, Aug 3, 2011 at 4:25 PM, Aaron Grewell wrote: > Example Config: > --- > :parser: YAML > :precedence: > - %{environment}/nodes/%{fqdn} > - %{environment}/nodes/cluster_%{cluster} > - %{environment}/nodes/site_%{site} > - %{environment}/nodes/default > :yaml: >:datadir: /usr/share/puppet/

Re: [Puppet Users] Extlookup() again.

- Original Message - > Argh, just realized I left something out of those paths, should be: This all works exactly as extlookup also worked, nothing new there. The general behavior is well documented even in the Puppet core docs -- You received this message because you are subscribed

Re: [Puppet Users] Extlookup() again.

Argh, just realized I left something out of those paths, should be: /usr/share/puppet/environments/testing/nodes/localhost.localdomain.yaml /usr/share/puppet/environments/testing/nodes/cluster_cluster1.yaml /usr/share/puppet/environments/testing/nodes/site_site1.yaml /usr/share/puppet/environments

Re: [Puppet Users] Extlookup() again.

Example Config: --- :parser: YAML :precedence: - %{environment}/nodes/%{fqdn} - %{environment}/nodes/cluster_%{cluster} - %{environment}/nodes/site_%{site} - %{environment}/nodes/default :yaml: :datadir: /usr/share/puppet/environments Example call: $default_packages = extlookup('linux_default_p

Re: [Puppet Users] Extlookup() again.

Lists (arrays) in YAML are represented with the `-' prefix. So you created a list called `testkey'. When you echo a list in Puppet, it concatenates the elements. That's why you got `DougBobBill' On Wed, Aug 3, 2011 at 4:19 PM, Douglas Garstang wrote: > On Wed, Aug 3, 2011 at 4:15 PM, Aaron Grewe

Re: [Puppet Users] Extlookup() again.

On Wed, Aug 3, 2011 at 4:15 PM, Aaron Grewell wrote: > Precedence is for having it look in multiple places. I've got node-level, > site-level, and default YAML files for example. > > On Wed, Aug 3, 2011 at 3:50 PM, Douglas Garstang > wrote: > >> Can't get the extlookup() that supports yaml to wo

Re: [Puppet Users] Extlookup() again.

Precedence is for having it look in multiple places. I've got node-level, site-level, and default YAML files for example. On Wed, Aug 3, 2011 at 3:50 PM, Douglas Garstang wrote: > Can't get the extlookup() that supports yaml to work. > > I did this... > > On server: > mv /usr/lib/ruby/site_ruby/

[Puppet Users] Extlookup() again.

Can't get the extlookup() that supports yaml to work. I did this... On server: mv /usr/lib/ruby/site_ruby/1.8/puppet/parser/functions/extlookup.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/functions/extlookup.rb.orig Replaced /usr/lib/ruby/site_ruby/1.8/puppet/parser/functions/extlookup.rb with p

Re: [Puppet Users] Extlookup() Docs

On Wed, Aug 3, 2011 at 10:37 AM, R.I.Pienaar wrote: > > > - Original Message - > > > > > > > > its not in puppet core and probably wont be, a more complete system > > > is @ http://www.devco.net/archives/tag/hiera > > > > > > > > > > > > > > > I realise it's not integrated into puppet. He

Re: [Puppet Users] Extlookup() Docs

I just copied it into the necessary locations on the master since I couldn't think of a use case for it elsewhere. On RHEL 5 I replaced: /usr/lib/ruby/site_ruby/1.8/puppet/parser/functions/extlookup.rb with puppet-extlookup/lib/puppet/parser/function

Re: [Puppet Users] Extlookup() Docs

- Original Message - > > > > > its not in puppet core and probably wont be, a more complete system > > is @ http://www.devco.net/archives/tag/hiera > > > > > > > > > > I realise it's not integrated into puppet. Hence the reason for > > asking how to integrate into puppet. In the pre

Re: [Puppet Users] Extlookup() Docs

On Wed, Aug 3, 2011 at 10:28 AM, R.I.Pienaar wrote: > > > - Original Message - > > > > On Wed, Aug 3, 2011 at 10:21 AM, R.I.Pienaar < r...@devco.net > wrote: > > > > > > > > > > > > > > > > - Original Message - > > > So the new extlookup that can apparently read YAML files, he

Re: [Puppet Users] Extlookup() Docs

- Original Message - > > On Wed, Aug 3, 2011 at 10:21 AM, R.I.Pienaar < r...@devco.net > wrote: > > > > > > > > - Original Message - > > So the new extlookup that can apparently read YAML files, here: > > > > > > http://www.devco.net/archives/2011/05/28/pluggable_ext

Re: [Puppet Users] Extlookup() Docs

On Wed, Aug 3, 2011 at 10:21 AM, R.I.Pienaar wrote: > > > - Original Message - > > So the new extlookup that can apparently read YAML files, here: > > > > > > > http://www.devco.net/archives/2011/05/28/pluggable_extlookup_for_puppet.php > > > > > > Are there any docs on how to actuall

Re: [Puppet Users] Extlookup() Docs

- Original Message - > So the new extlookup that can apparently read YAML files, here: > > > http://www.devco.net/archives/2011/05/28/pluggable_extlookup_for_puppet.php > > > Are there any docs on how to actually install? I need a _little_ more > than a reference to the source cod

[Puppet Users] Extlookup() Docs

So the new extlookup that can apparently read YAML files, here: http://www.devco.net/archives/2011/05/28/pluggable_extlookup_for_puppet.php Are there any docs on how to actually install? I need a _little_ more than a reference to the source code on github Doug. -- You received this mes

[Puppet Users] Extlookup and stages

Hi, I've seen some weird behaviour using extlookup, and wondered if anyone has seen it too... Basically it seems that if the $extlookup_* variables are defined in site.pp then an early stage use of extlookup doesn't see these variables at all, yet main stage ones do. I added some debug statements

Re: [Puppet Users] extlookup error

On 8.6.2011 13:54, R.I.Pienaar wrote: > yes, it works. you need to be sure to run the extlookup.rb that > comes with the new puppet not the old one I had removed extlookup.rb from my module but now I found another instance of extlookup in libdir on puppetmaster. Working now. Thank You. > > --

Re: [Puppet Users] extlookup error

hey, yes, it works. you need to be sure to run the extlookup.rb that comes with the new puppet not the old one - Original Message - > Hi, > > Until now I used puppet 0.25.5. I tried upgrading to 2.6.8 > extlookup does not work for me anymore > > err: Could not retrieve catalog from rem

[Puppet Users] extlookup error

Hi, Until now I used puppet 0.25.5. I tried upgrading to 2.6.8 extlookup does not work for me anymore err: Could not retrieve catalog from remote server: Error 400 on SERVER: undefined local variable or method `parser' for # at /var/puppet/data-prod/manifests/XXX/nodes.pp:17 on node XXX I remove

[Puppet Users] Extlookup++

On Fri, May 27, 2011 at 1:08 PM, R.I.Pienaar wrote: > And for what its worth this afternoon just to see how hard it is > and to again ask to myself 'wtf has no-one done this yet?' and also > 'wtf are people at Puppet Labs reinventing this wheel?' I wrote > a new extlookup that has pluggable backe

Re: [Puppet Users] extlookup == bad?

On 04/12/2011 08:24 PM, R.I.Pienaar wrote: > This demonstrates the problem. You have had to spend time working > with customers to explain how to build these. It's a very complex > subject, something our target audience in many cases dont get. They > do understand extlookup though and it does s

Re: [Puppet Users] extlookup == bad?

- Original Message - > > > > On Tue, Apr 12, 2011 at 12:54 AM, R.I.Pienaar < r...@devco.net > > > wrote: > > - Original Message - > > > > > > > > > > > > On Mon, Apr 11, 2011 at 9:25 PM, John Warburton < > > > jwarbur...@gmail.com > wrote: > > > > > > > > > OK, I'll bite > >

Re: [Puppet Users] extlookup == bad?

On Tue, Apr 12, 2011 at 11:24 AM, R.I.Pienaar wrote: > > > - Original Message - > > Hi all, > > > > Thanks for the input > > > > > > On Tue, Apr 12, 2011 at 12:54 AM, R.I.Pienaar < r...@devco.net > > > wrote: > > - Original Message - > > > > > > > > > > > > On Mon, Apr 11, 2011 at

Re: [Puppet Users] extlookup == bad?

- Original Message - > Hi all, > > Thanks for the input > > > On Tue, Apr 12, 2011 at 12:54 AM, R.I.Pienaar < r...@devco.net > > wrote: > - Original Message - > > > > > > > > On Mon, Apr 11, 2011 at 9:25 PM, John Warburton < > > jwarbur...@gmail.com > wrote: > > > > > > OK

Re: [Puppet Users] extlookup == bad?

On Tue, Apr 12, 2011 at 8:00 AM, R.I.Pienaar wrote: > > > - Original Message - > > On 04/12/2011 04:41 PM, R.I.Pienaar wrote: > > > > > > > > > - Original Message - > > >> On Tue, Apr 12, 2011 at 12:54 AM, R.I.Pienaar < r...@devco.net > > > >> wrote: > > >> > > >> > > >> > > >> Th

Re: [Puppet Users] extlookup == bad?

Hi all, Thanks for the input On Tue, Apr 12, 2011 at 12:54 AM, R.I.Pienaar wrote: > > > - Original Message - > > > > > > > > On Mon, Apr 11, 2011 at 9:25 PM, John Warburton < > > jwarbur...@gmail.com > wrote: > > > > > > OK, I'll bite > > > > In the newly published Style Guide ( > > htt

Re: [Puppet Users] extlookup == bad?

- Original Message - > On 04/12/2011 04:41 PM, R.I.Pienaar wrote: > > > > > > - Original Message - > >> On Tue, Apr 12, 2011 at 12:54 AM, R.I.Pienaar < r...@devco.net > > >> wrote: > >> > >> > >> > >> The PDL is a *much* more desirable solution than either layered > >> classes >

Re: [Puppet Users] extlookup == bad?

On 04/12/2011 04:41 PM, R.I.Pienaar wrote: > > > - Original Message - >> On Tue, Apr 12, 2011 at 12:54 AM, R.I.Pienaar < r...@devco.net > >> wrote: >> >> >> >> The PDL is a *much* more desirable solution than either layered >> classes >> or extlookup, why it has gone un-implemented I dont

Re: [Puppet Users] extlookup == bad?

- Original Message - > On Tue, Apr 12, 2011 at 12:54 AM, R.I.Pienaar < r...@devco.net > > wrote: > > > > The PDL is a *much* more desirable solution than either layered > classes > or extlookup, why it has gone un-implemented I dont know and why the > current suggestion is that layered

Re: [Puppet Users] extlookup == bad?

On Tue, Apr 12, 2011 at 12:54 AM, R.I.Pienaar wrote: > The PDL is a *much* more desirable solution than either layered classes > or extlookup, why it has gone un-implemented I dont know and why the > current suggestion is that layered classes somehow represents an effective > alternative to the P

Re: [Puppet Users] extlookup == bad?

- Original Message - > > > > On Mon, Apr 11, 2011 at 9:25 PM, John Warburton < > jwarbur...@gmail.com > wrote: > > > OK, I'll bite > > In the newly published Style Guide ( > http://docs.puppetlabs.com/guides/style_guide.html ), right at the > end it says > > Modules should avoid th

Re: [Puppet Users] extlookup == bad?

On Mon, Apr 11, 2011 at 9:25 PM, John Warburton wrote: > OK, I'll bite > > In the newly published Style Guide ( > http://docs.puppetlabs.com/guides/style_guide.html), right at the end it > says > > Modules should avoid the use of extlookup() in favor of ENCs or other > alternatives > For clar

[Puppet Users] extlookup == bad?

OK, I'll bite In the newly published Style Guide ( http://docs.puppetlabs.com/guides/style_guide.html), right at the end it says Modules should avoid the use of extlookup() in favor of ENCs or other alternatives But there is no reason as to why. We have a rule of thumb where we use the ENC

[Puppet Users] extlookup debugging

Hi All We are going through a tedious debug looking for a nit with our extlookup data. I wondered if there was any way to get progress/status from extlookup to help us find our problem It seems R.I.Pienaar has some debug code for extlookup ( http://groups.google.com/group/puppet-dev/msg/5c7062183

Re: [Puppet Users] Extlookup in external nodes

If you're using 2.6 you can make a pure ruby class that will look at each variable and see if its value is a function if it is, call that function. However, I don't know how to replace the value of the variable with what re function returns. You can get the basic concept I'm talking about here:

Re: [Puppet Users] Extlookup in external nodes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > The yaml isn't being auto generated by anything. All the external node > script does it reprint it. This was by design because I am dead set against > putting the configuration into anything except files. The issue is that parameters is just a yaml

Re: [Puppet Users] Extlookup in external nodes

Darn. I was hoping I could. The yaml isn't being auto generated by anything. All the external node script does it reprint it. This was by design because I am dead set against putting the configuration into anything except files. Doug. On Mon, Dec 6, 2010 at 12:13 PM, Peter Meier wrote: > -

Re: [Puppet Users] Extlookup in external nodes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 12/06/2010 09:01 PM, Douglas Garstang wrote: > I don't suppose I can do this in an external node, can I? no but you can probably tune your extlookup tool to do that for you, before it spits out the yaml for the puppetmaster. ~pete -BEGIN P

[Puppet Users] Extlookup in external nodes

I don't suppose I can do this in an external node, can I? classes: - network::config::app_bonded environment: production parameters: password : extlookup("password", "", "default_${domain}") Doug. -- You received this message because you are subscribed to the Google Groups "Puppet Use

Re: [Puppet Users] extlookup in 2.6.1 defaults

On Sun, Aug 22, 2010 at 12:20 AM, Douglas Garstang wrote: > On Sun, Aug 22, 2010 at 12:02 AM, Joe McDonagh > wrote: >> On 08/22/2010 02:42 AM, Douglas Garstang wrote: >> >>> >>> This seems a bit weird to me. The second parameter isn't optional (I >>> think the 2nd and 3rd parameters should be swi

Re: [Puppet Users] extlookup in 2.6.1 defaults

On Sun, Aug 22, 2010 at 12:02 AM, Joe McDonagh wrote: > On 08/22/2010 02:42 AM, Douglas Garstang wrote: > >> >> This seems a bit weird to me. The second parameter isn't optional (I >> think the 2nd and 3rd parameters should be switched), which means that >> you MUST have a default value in there,

Re: [Puppet Users] extlookup in 2.6.1 defaults

On 08/22/2010 02:42 AM, Douglas Garstang wrote: > > This seems a bit weird to me. The second parameter isn't optional (I > think the 2nd and 3rd parameters should be switched), which means that > you MUST have a default value in there, which means, you might as well > use the same value as in the

[Puppet Users] extlookup in 2.6.1 defaults

Hmmm So I was just trying the extlookup function that comes with puppet 2.6.1. It now lets you do this: $version = extlookup("rsyslog_version", "present", "packages") which, according to the documentation: # This will look for a version configured in packages.csv and then in the rest as con