[Puppet Users] custom facts

i'm upgrading from puppet 3 (via epel) to puppet 5 (via puppetlabs), i'm confused on how/if there's a way to get custom ruby facts to load into facter without having to specify FACTERLIB. i'll admit i might have missed something in the documentation in the past i'd copy my ruby facts into

Re: [Puppet Users] Custom Facts using awk

Wow is that a lot to take in. I simply need to learn Ruby to cut down on noise, or so it seems. Thanks Michael. -- Warron French On Thu, Mar 30, 2017 at 12:23 PM, Michael Watters wrote: > %x is a ruby method which captures command output. IMO

Re: [Puppet Users] Custom Facts using awk

%x is a ruby method which captures command output. IMO you can do most of what you need using native ruby methods, there's no need to pipe output to grep/sed/awk since ruby has built in pattern matching functions and if you're using ruby you might as well do it the ruby way. For example, this

Re: [Puppet Users] Custom Facts using awk

On Thursday, 30 March 2017 16:11:35 UTC+1, Warron French wrote: > > Hi Luke, I have some questions for you. > > First, the link= > https://github.com/puppetlabs/puppetlabs-apache/blob/master/lib/facter/apache_version.rb > > didn't have any reference to awk at all, was this the file you intended

Re: [Puppet Users] Custom Facts using awk

Hi Luke, I have some questions for you. First, the link= https://github.com/puppetlabs/puppetlabs-apache/blob/master/lib/facter/apache_version.rb didn't have any reference to awk at all, was this the file you intended to suggest? Secondly, the link=

Re: [Puppet Users] Custom Facts using awk

Hey, thanks for the examples Luke! I am looking at them now. -- Warron French On Thu, Mar 30, 2017 at 8:31 AM, Luke Bigum wrote: > Puppet modules on Github are a good source. I've found a simple one: > >

Re: [Puppet Users] Custom Facts using awk

Puppet modules on Github are a good source. I've found a simple one: https://github.com/puppetlabs/puppetlabs-apache/blob/master/lib/facter/apache_version.rb And one of my own that's a little more complicated:

Re: [Puppet Users] Custom Facts using awk

Joshua, thanks for this feedback. I don't really know ruby; can you offer some ideas of where I can find other Puppet Facts written in Ruby that don't look like my originally posted example? Thank you sir. -- Warron French On Tue, Mar 28, 2017 at 10:51 AM, Joshua

Re: [Puppet Users] Custom Facts using awk

Excellent. Good to know. I was told otherwise. Thanks, Joshua Schaeffer On Wednesday, March 29, 2017 at 7:11:55 AM UTC-6, Gabriel Schuyler wrote: > > Never fear, external facts work just fine in Puppet 3. > > On Tuesday, March 28, 2017 at 10:51:52 AM UTC-4, Joshua Schaeffer wrote: >> >> External

Re: [Puppet Users] Custom Facts using awk

Never fear, external facts work just fine in Puppet 3. On Tuesday, March 28, 2017 at 10:51:52 AM UTC-4, Joshua Schaeffer wrote: > > External facts are a Puppet v4 feature only. You have to use Ruby to > create custom facts in Puppet v3. > > On Monday, March 27, 2017 at 3:54:00 PM UTC-6, Warron

Re: [Puppet Users] Custom Facts using awk

External facts are a Puppet v4 feature only. You have to use Ruby to create custom facts in Puppet v3. On Monday, March 27, 2017 at 3:54:00 PM UTC-6, Warron French wrote: > > OK, done, and done. But it still isn't showing up. > > Is this potentially because I am using PE-3.8 as a component of

Re: [Puppet Users] Custom Facts using awk

OK, done, and done. But it still isn't showing up. Is this potentially because I am using PE-3.8 as a component of Red Hat Satellite? -- Warron French On Mon, Mar 27, 2017 at 5:28 PM, Peter Bukowinski wrote: > Hi Warron, > > Puppet executes the

Re: [Puppet Users] Custom Facts using awk

Hi Warron, Puppet executes the script directly, so you need the shebang line and you must ensure the file is executable. -- Peter > On Mar 27, 2017, at 2:25 PM, warron.french wrote: > > Peter, perhaps I misunderstood you; but, I thought I was supposed to be able >

Re: [Puppet Users] Custom Facts using awk

Peter, perhaps I misunderstood you; but, I thought I was supposed to be able to use bash or sh scripting to generate facters of my own without the use of Ruby. The link you provided refers to a python script example. It also adds a shebang line at the top of the script; do I need the shebang

Re: [Puppet Users] Custom Facts using awk

Sorry, I may have been ambiguous with the file extensions. A text file should end in .txt. This means you define external facts like this: # This is a plain text file that defines two external facts my_fact1=my_value1 my_fact2=my_value2 An executable program or script should end in whatever

Re: [Puppet Users] Custom Facts using awk

Yes, you can put multiple key=value pairs in a single file. Puppet v4 supports three known types: 1. YAML (must end in .yaml) 2. JSON (must end in .json) 3. Text (must end in .txt) When working with .txt files you can only define string values. Arrays and hashes are not supported.

Re: [Puppet Users] Custom Facts using awk

On Wed, Mar 22, 2017 at 4:07 PM Peter Bukowinski wrote: > Hi Warron, > > I'd consider using an external, executable fact to avoid ruby altogether. > > > https://docs.puppet.com/facter/3.6/custom_facts.html#executable-facts-unix > > Basically, you can write a bash script (or

Re: [Puppet Users] Custom Facts using awk

Thanks Rob. I will try both approaches; for me there is more appeal in simply using a shell script. Peter, can I generate multiple key=value pairs inside the same shell script? I don't explicitly have to do it the way you presented with key="key_name" value="evaluated_expression" echo

Re: [Puppet Users] Custom Facts using awk

Oh wow! That cool! Thanks for the different method Peter! -- Warron French On Wed, Mar 22, 2017 at 7:07 PM, Peter Bukowinski wrote: > Hi Warron, > > I'd consider using an external, executable fact to avoid ruby altogether. > >

Re: [Puppet Users] Custom Facts using awk

That's probably one of the best ways to do this. But... You CAN use double quotes around a string. You will need to escape characters that will otherwise be interpolated like double quotes and dollar signs. I'm going off memory but I think `"awk '{print \$1_\$2}'"` should interpolate to `awk

Re: [Puppet Users] Custom Facts using awk

Hi Warron, I'd consider using an external, executable fact to avoid ruby altogether. https://docs.puppet.com/facter/3.6/custom_facts.html#executable-facts-unix Basically, you can write a bash script (or use any language you want), drop it into '//facts.d/' on your puppet server, and it

[Puppet Users] Custom Facts using awk

Hello, I have finally learned how to write a Custom Fact; and duplicated the syntax several times over inside the same .rb file. I am using syntax that looks like the following: Facter.add('qty_monitors_total') do setcode do Facter::Util::Resolution.exec('/bin/grep "

[Puppet Users] Custom facts are updated in the next execution of "puppet agent --test"

Hi, I am using following code snippet in one of the init.pp file of puppet master to load the updated facts in "facts.yaml" available in "C:\marionette-collective\etc\" folder. file { "c:/marionette-collective/etc/facts.yaml": loglevel => debug, content =>

Re: [Puppet Users] Custom facts are updated in the next execution of "puppet agent --test"

Amrit, since you are deploying it as a file resource, it has to be deployed to the agent before it will be used. You could instead add the fact to your module, where plugin sync will push it to the agent before it collects facts, which means it is there on the first facts run. See

[Puppet Users] Custom facts are updated in the next execution of "puppet agent --test"

Hi, I am using following code snippet in one of the init.pp file of puppet master to load the updated facts in "facts.yaml" available in "C:\marionette-collective\etc\" folder. file { "c:/marionette-collective/etc/facts.yaml": loglevel => debug, content => inline_template("<%=

[Puppet Users] Custom facts with exclusions

Hi All, I'm generating custom facts and want to exclude few software's in black list. Ex: 7-Zip is a software causing a problem as its name starts with digit and not a letter. The name also has some spaces, hiphens. file { "c:/marionette-collective/etc/facts.yaml": loglevel => debug,

[Puppet Users] Custom Facts for windows with powershell

Hi, I'm trying to create a custom fact to get the installed software using powershell command in windows as follows... *PS Command:-* Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | where{$_.DisplayName -and $_.displayname -notmatch 'Update'} | Select-Object

Re: [Puppet Users] Custom facts per node.. only via /etc/facter/facts.d/fact_xyz.txt per node?

--- Original Message - From: "Hubert Schmoll" <hubertschm...@googlemail.com> To: "Puppet Users" <puppet-users@googlegroups.com> Cc: s...@tetralog.de Sent: Friday, 4 December, 2015 9:31:33 AM Subject: [Puppet Users] Custom facts per node.. only via /etc/facter/fac

[Puppet Users] Custom facts per node.. only via /etc/facter/facts.d/fact_xyz.txt per node?

Hello everyone, here's what i wanna accomplish: i am havin 4 so called servergroups - ci - dev - stage - production and i want them to have specific facts depending on the group they are in. so in every node i created a file /etc/facter/facts.d/servergroup.txt, containing e.g.

Re: [Puppet Users] Custom facts in facter

Hello, this is working. Thank you ! Hugo On 21 October 2015 at 19:06, Peter Bukowinski wrote: > > > On Oct 21, 2015, at 12:56 PM, Hugo Deprez wrote: > > > > Hello, > > > > I created a custom fact with the following procedure : > > > > mkdir -p

Re: [Puppet Users] Custom facts in facter

> On Oct 21, 2015, at 12:56 PM, Hugo Deprez wrote: > > Hello, > > I created a custom fact with the following procedure : > > mkdir -p /etc/puppet/modules/facts/lib/facter > touch apache.rb > > Content of apache.rb file : > Facter.add('apache') do > setcode do >

[Puppet Users] Custom facts in facter

Hello, I created a custom fact with the following procedure : mkdir -p /etc/puppet/modules/facts/lib/facter touch apache.rb Content of apache.rb file : Facter.add('apache') do setcode do apache_package = Facter::Core::Execution.exec('which apache2') # if 'which apache2' exits with

[Puppet Users] custom facts sensitive to spaces

I think I found a bug in facter in 3.8.2 but wanted to ask here before opening a PL ticket. Basic description is that facter has different behaviors if you run it without vs. with a fact specified. To recreate: # echo 'foo = bar' > /etc/facter/facts.d/foo.txt # facter | grep foo foo => bar

Re: [Puppet Users] custom facts sensitive to spaces

On Tue, Sep 08, 2015 at 11:47:44AM -0700, Vince Skahan wrote: >I think I found a bug in facter in 3.8.2 but wanted to ask here before >opening a PL ticket. > >Basic description is that facter has different behaviors if you run it >without vs. with a fact specified. > >To

[Puppet Users] Custom facts ordering / full package name

Hi everybody. I got a question about puppet. I have a case which I would like to run all the statements in order and one of them is a custom fact that I created and the return is assigned to a variable but I got an error when I do that ( Syntax error at '='; expected '}' at ... ) , the

Re: [Puppet Users] custom facts

Thanks for the Reply Felix. I found out my mistake. my script was not providing the data in the key=value format. I modified the script and now works fine. Thanks for asking!! Cheers and Happy Vacation! With Warm Regards Kaustubh.A.Chaudhari (M)-09373102619 On Tue, Dec 23, 2014 at 7:02 PM,

Re: [Puppet Users] custom facts

On 12/22/2014 04:39 PM, kaustubh chaudhari wrote: I was expecting o/p as. Disk_Size C: 30GB So what do you get instead? Have you added debug logging to your script to find out whether Facter invokes it at all? -- You received this message because you are subscribed to the Google Groups

[Puppet Users] custom facts

Hi All, I am trying to run a batch script from custom facts. But unable to get the required output. I know i am doing some thing wrong, but where. == Facter.add(:Disk_Size) do confine :kernel = windows setcode do Facter::Util::Execution.exec(C:\\Windows\\System32\\cmd.exe

Re: [Puppet Users] custom facts ir plugin facts

On Friday, November 28, 2014 7:03:54 PM UTC-6, pankaj sehgal wrote: Thanks for the reply. I m not cloaking any fact just trying to know in a general puppet run how it should go?? If you cannot tell the difference then what does it matter? Or to put it the other way around, why is it

[Puppet Users] custom facts ir plugin facts

Hi Anyone can please help me to sort out whether custom facts are loaded first or build-in facts in the puppet master. Thanks -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it,

[Puppet Users] custom facts ir plugin facts

Hi Anyone can please help me to sort out whether custom facts are loaded first or build-in facts in the puppet master. Thanks -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it,

Re: [Puppet Users] custom facts ir plugin facts

Facts are generated by the Puppet client (agent) then given to the master. The only reason ordering between custom and built in facts would matter is if you ware trying to 'cloak' a fact. I think what you should do is make a custom fact, then use that in your manifests. -- Spencer Krum

Re: [Puppet Users] custom facts ir plugin facts

Thanks for the reply. I m not cloaking any fact just trying to know in a general puppet run how it should go?? -- You received this message because you are subscribed to the Google Groups Puppet Users group. To unsubscribe from this group and stop receiving emails from it, send an email to

[Puppet Users] Custom facts and environments

I'm attempting to make the jump to directory-based environments and am curious about what to do with custom facts. In my current config I've tried putting custom facts into a separate module as /etc/puppet/modules/facts/{manifest,lib} and /etc/puppet/modules/facts/lib/facter/modules go here. I

[Puppet Users] Custom facts variables coming out empty on manifest

Hi all. I have a very simple Custom Fact in /etc/puppet/modules/facts/lib/facter/php_version.rb : Facter.add(:php_version) do setcode do Facter::Util::Resolution.exec('php-config --version|awk -F . \'{print $1$2}\'') end end It gets deployed and if I run facter -p |grep php on the

Re: [Puppet Users] Custom facts variables coming out empty on manifest

Hi, Perhaps there is an environment diference between the command line and the puppet agent process. The first one I think is the path one. I would try to launch the php-config --version and the awk with the full-path. If that doesn't work, I would check if the php-config-version needs any

Re: [Puppet Users] Custom facts not working

Good point John, though you must remember a lot of users utilise cron to drive the puppet run's on standalone and agents. So this environment variable is important , especially for cloud based deployments that don't use a puppet master. Certainly with Ubuntu servers in standalone mode, I have

Re: [Puppet Users] Custom facts not working

On Thursday, April 4, 2013 5:12:21 AM UTC-5, Codfather wrote: Good point John, though you must remember a lot of users utilise cron to drive the puppet run's on standalone and agents. I'm well aware of that. So this environment variable is important , especially for cloud based

Re: [Puppet Users] Custom facts not working

Worth noting that if you set this environment variable in one of your shell environment config files , like .bashrc, you would need to export it. Like this export FACTERLIB=/var/lib/puppet/lib/facter regards Nick On Monday, 3 October 2011 12:14:30 UTC+2, Stefan Schulte wrote: On Mon, Oct

Re: [Puppet Users] Custom facts not working

On Wednesday, April 3, 2013 2:44:22 AM UTC-5, Codfather wrote: Worth noting that if you set this environment variable in one of your shell environment config files , like .bashrc, you would need to export it. Like this export FACTERLIB=/var/lib/puppet/lib/facter True, but it's even

[Puppet Users] Custom Facts accessible via Facter

I don't get it. I just wrote a simple test custom fact in ruby (ugh, I hate ruby) and was able to access it as a variable on the client side. However, it doesn't appear in the facter output. Is is supposed to? Doug -- You received this message because you are subscribed to the Google Groups

Re: [Puppet Users] Custom Facts accessible via Facter

Try Facter - p Regards Am 16.08.2012 um 07:43 schrieb Douglas Garstang doug.garst...@gmail.com: I don't get it. I just wrote a simple test custom fact in ruby (ugh, I hate ruby) and was able to access it as a variable on the client side. However, it doesn't appear in the facter output.

Re: [Puppet Users] Custom Facts accessible via Facter

On Wed, Aug 15, 2012 at 10:46 PM, Florian Koch florian.koch1...@gmail.com wrote: Try Facter - p Regards Thanks. Didn't know about that. Now, back to scraping my eyeballs with a blunt rusty razor blade, err looking at ruby code. Doug. -- You received this message because you are

Re: [Puppet Users] Custom Facts

As I think has been mentioned, use :confine to limit on which node this fact is listed. All facts are distributed to all nodes. Cheers On 09/08/2012, at 15:21, Yaniv Fine yanivf...@gmail.com wrote: In general . I am trying to parse a variable i have in a file in few of my servers and add it

Re: [Puppet Users] Custom Facts

On Aug 9, 2012, at 4:46 AM, Denmat wrote: As I think has been mentioned, use :confine to limit on which node this fact is listed. All facts are distributed to all nodes. Cheers Would this include local facts created with puppetlabs-stdlib:/etc/facter/facts.d ? Or are you referring to

Re: [Puppet Users] Custom Facts

On Tuesday, August 7, 2012 8:45:45 AM UTC-5, Yaniv Fine wrote: well its wroking for me now . newbie question . if i put the test.rb file inside modules/common/test/lib/facter/test.rb is it normal that it runs automatically on all servers without a way for me to control what machine

Re: [Puppet Users] Custom Facts

what is i put the rb file in another dir bellow the module dir . any way i can control what node will load it ? On Wed, Aug 8, 2012 at 5:16 PM, jcbollinger john.bollin...@stjude.orgwrote: On Tuesday, August 7, 2012 8:45:45 AM UTC-5, Yaniv Fine wrote: well its wroking for me now . newbie

Re: [Puppet Users] Custom Facts

On Wednesday, August 8, 2012 10:06:27 AM UTC-5, Yaniv Fine wrote: what is i put the rb file in another dir bellow the module dir . any way i can control what node will load it ? I don't know, but I think it unlikely that you could get some nodes to run it but not others. What are you

Re: [Puppet Users] Custom Facts

In general . I am trying to parse a variable i have in a file in few of my servers and add it as a fact i can than use in a module . This specific file that reside in few of my servers have looks like value : var .inside the rb file i do facter.add .and add the value to a fact .there is no reson

Re: [Puppet Users] Custom Facts

Hi Dan . thank you for your help and pointers . i need your advice pls . lets say i have /tmp/yanivf.txt inside i have a line testing when i run require 'facter' Facter.add(yaniv) do setcode do 'cat /tmp/yanivf.txt' end end and than i run facter i get nothing when i run export

Re: [Puppet Users] Custom Facts

Since you are directly executing a command, you really want to use the built-it Puppet function here: require 'facter' Facter.add(yaniv) do setcode do Facter::Util::Resolution.exec(cat /tmp/yanivf.txt) end end There is probably some newlines that file that may not be immediately

Re: [Puppet Users] Custom Facts

Thank you for your answer . any reson why Facter::Util::Resolution. exec not working . i don't see either when running factor on the client or on the puppet server yaml file any record of fact named yaniv ? On Tue, Aug 7, 2012 at 12:49 PM, Foster Rilindo rili...@mac.com wrote: Since you are

Re: [Puppet Users] Custom Facts

On Tuesday, August 7, 2012 4:59:01 AM UTC-5, Yaniv Fine wrote: Thank you for your answer . any reson why Facter::Util::Resolution. exec not working . i don't see either when running factor on the client or on the puppet server yaml file any record of fact named yaniv ? Have you

Re: [Puppet Users] Custom Facts

well its wroking for me now . newbie question . if i put the test.rb file inside modules/common/test/lib/facter/test.rb is it normal that it runs automatically on all servers without a way for me to control what machine will run it ? all my modules reside : modules/common/apache java .. On

[Puppet Users] Custom Facts

Hi experts . i would like to write a custom fact the will add a fact to a machine yaml file i am a file /etc/file.conf inside this file a have many lines like value1 = test1 value2 = test2 i want to create a custom rb file that will grep test2 from value2 value from /etc/file.conf ,

Re: [Puppet Users] Custom Facts

Can this be file in other path ? On Aug 6, 2012 4:20 PM, Dan White y...@comcast.net wrote: I think you are trying to re-invent a wheel that is already in use. Consider: http://puppetlabs.com/blog/module-of-the-week-puppetlabsstdlib-puppetlabs-standard-library-part-3/ facter-dot-d; a simple

Re: [Puppet Users] Custom Facts

Let me re-answer that: Using the stdlib::facter-dot-d, I expect you are restricted to /etc/facts.d However, if you look at the examples here ( http://puppetlabs.com/blog/facter-part-1-facter-101/ ), you can create facts that reference files anywhere in the system. The example shows using a

Re: [Puppet Users] Custom facts and hyphens

On 06/21/2012 12:30 AM, Jo Rhett wrote: I'm not saying that you're wrong, but I'm still struggling to see this. Every place that class names are used should be single quoted, according to your style guide. And it's very easy in a syntax to tell the different between 'test-jo + 2' and 'test -

Re: [Puppet Users] Custom facts and hyphens

- Original Message - From: Felix Frank felix.fr...@alumni.tu-berlin.de To: puppet-users@googlegroups.com Sent: Thursday, June 21, 2012 10:18:50 AM Subject: Re: [Puppet Users] Custom facts and hyphens On 06/21/2012 12:30 AM, Jo Rhett wrote: I'm not saying that you're wrong

Re: [Puppet Users] Custom facts and hyphens

On Jun 21, 2012, at 2:18 AM, Felix Frank wrote: On 06/21/2012 12:30 AM, Jo Rhett wrote: I'm not saying that you're wrong, but I'm still struggling to see this. Every place that class names are used should be single quoted, according to your style guide. And it's very easy in a syntax to tell

[Puppet Users] Custom facts and hyphens

Hi all, Possibly related to http://projects.puppetlabs.com/issues/10146 but I wanted to get a second opinion. I have a custom fact that iteratse through the disks on a given EC2 node and creates facts for block devices based on their /dev/disk/by-path/ links. I had to come up with this as a

Re: [Puppet Users] Custom facts and hyphens

- Original Message - From: Steph Gosling st...@chuci.org To: puppet-users@googlegroups.com Sent: Wednesday, June 20, 2012 1:20:12 PM Subject: [Puppet Users] Custom facts and hyphens Hi all, Possibly related to http://projects.puppetlabs.com/issues/10146 but I wanted to get

Re: [Puppet Users] Custom facts and hyphens

On Jun 20, 2012, at 3:02 PM, Nick Fagerlund wrote: What R.I. said. Hyphens in variable names and class names are a no-no, although they kinda work in some versions of Puppet. Use underscores instead. (Why are hyphens a problem? Well, partly because you can subtract variables in

[Puppet Users] Custom facts question on windows 2008 R2

Hi guys, I'm trying to define a custom fact on windows puppet agent, I'm using the version 2.7.14. I made a powershell that checks for the state of a service and return true or false. If I execute it on powershell I got this: PS C:\programdata\PuppetLabs\facter\ext .\udp_status.ps1

[Puppet Users] custom facts loaded twice

Hi all, Every time I run puppet manually I see the message: # puppetd --test --server $SERVER info: Retrieving plugin info: Loading facts in hwtype info: Loading facts in odd_ip info: Loading facts in default_gateway info: Loading facts in hwtype info: Loading facts in odd_ip info: Loading facts

Re: [Puppet Users] custom facts loaded twice

On Tue, Dec 20, 2011 at 6:32 AM, Arnau Bria listsar...@gmail.com wrote: Hi all, Every time I run puppet manually I see the message: # puppetd --test --server $SERVER info: Retrieving plugin info: Loading facts in hwtype info: Loading facts in odd_ip info: Loading facts in default_gateway

Re: [Puppet Users] custom facts loaded twice

I'm seeing this too, Debian 5.0.9 / puppet 2.7.9. On Tue, Dec 20, 2011 at 16:32, Arnau Bria listsar...@gmail.com wrote: Hi all, Every time I run puppet manually I see the message: # puppetd --test --server $SERVER info: Retrieving plugin info: Loading facts in hwtype info: Loading facts

[Puppet Users] Custom facts not working

Hi all, I'm experiencing some difficulty getting custom facts to run. I've installed them on the puppetmaster in: ${modulepath}/${module}/lib/facter/*.rb and from there they appear to be copied properly onto the clients, where they end up in: /var/lib/puppet/lib/facter/*.rb On all

Re: [Puppet Users] Custom facts not working

On Mon, Oct 03, 2011 at 11:00:18AM +0100, Jonathan Gazeley wrote: Hi all, I'm experiencing some difficulty getting custom facts to run. I've installed them on the puppetmaster in: ${modulepath}/${module}/lib/facter/*.rb and from there they appear to be copied properly onto the clients,

Re: [Puppet Users] Custom facts not working

On 03/10/11 11:14, Stefan Schulte wrote: On Mon, Oct 03, 2011 at 11:00:18AM +0100, Jonathan Gazeley wrote: Hi all, I'm experiencing some difficulty getting custom facts to run. I've installed them on the puppetmaster in: ${modulepath}/${module}/lib/facter/*.rb and from there they appear to

Re: [Puppet Users] Custom facts not working

On Mon, Oct 03, 2011 at 12:08:23PM +0100, Jonathan Gazeley wrote: On 03/10/11 11:14, Stefan Schulte wrote: On Mon, Oct 03, 2011 at 11:00:18AM +0100, Jonathan Gazeley wrote: Hi all, I'm experiencing some difficulty getting custom facts to run. I've installed them on the puppetmaster in:

Re: [Puppet Users] Custom facts not working

Stefan Schulte wrote: I guess facter as a standalone executable doesn't look into /var/lib/puppet. Try running FACTERLIB=/var/lib/puppet/lib/facter facter as described in the custom facts guide [1] [1] http://docs.puppetlabs.com/guides/custom_facts.html#an-example Or use the -p |

Re: [Puppet Users] Custom facts not working

On 03/10/11 14:24, Todd Zullinger wrote: Stefan Schulte wrote: I guess facter as a standalone executable doesn't look into /var/lib/puppet. Try running FACTERLIB=/var/lib/puppet/lib/facter facter as described in the custom facts guide [1] [1]

Re: [Puppet Users] Custom Facts

On 2/09/11 3:03 PM, Douglas Garstang wrote: I really appreciate your reply, but I've inherited a mess that isn't easy to fix, and the most appropriate solution for right now isn't always the best solution. When the boss says GET IT DONE, you don't have time to refactor someone elses mess and

Re: [Puppet Users] Custom Facts

In case you decide to go with an ENC, here's the one we use. It takes a YAML file for each host providing environment, classes, and parameters to be used. All node-specific data is kept in the same YAML file and either provided via the ENC or pulled in via Hiera at the class level.

Re: [Puppet Users] Custom Facts

On Thu, Sep 1, 2011 at 10:30 PM, Matt Moor m...@imprecise.org wrote: On 2/09/11 3:03 PM, Douglas Garstang wrote: I really appreciate your reply, but I've inherited a mess that isn't easy to fix, and the most appropriate solution for right now isn't always the best solution. When the boss

Re: [Puppet Users] Custom Facts

- Original Message - At the end of the day, this all seems to be a limitation with mcollective. It can only read facts from one source, either facter or a yaml file. I believe facter is the current source, and people have written scripts that rely on that. I can write a custom

Re: [Puppet Users] Custom Facts

On Fri, Sep 2, 2011 at 11:26 AM, R.I.Pienaar r...@devco.net wrote: - Original Message - At the end of the day, this all seems to be a limitation with mcollective. It can only read facts from one source, either facter or a yaml file. I believe facter is the current source, and

Re: [Puppet Users] Custom Facts

On Fri, Sep 2, 2011 at 12:06 PM, Douglas Garstang doug.garst...@gmail.comwrote: On Fri, Sep 2, 2011 at 11:26 AM, R.I.Pienaar r...@devco.net wrote: - Original Message - At the end of the day, this all seems to be a limitation with mcollective. It can only read facts from one

[Puppet Users] Custom Facts

So, after reading this doc: http://projects.puppetlabs.com/projects/1/wiki/Adding_Facts it's not readily apparent to me how I can create facts that are derived from variables defined at the node level in puppet, rather than at the O/S level on the client. I want to be able to set a variable that

Re: [Puppet Users] Custom Facts

You can't. The whole purpose of facts is to allow Puppet to make decisions based on client data. Variables=server, facts=client. On Thu, Sep 1, 2011 at 3:41 PM, Douglas Garstang doug.garst...@gmail.comwrote: So, after reading this doc:

Re: [Puppet Users] Custom Facts

On Thu, Sep 1, 2011 at 4:31 PM, Aaron Grewell aaron.grew...@gmail.comwrote: You can't. The whole purpose of facts is to allow Puppet to make decisions based on client data. Variables=server, facts=client. Yep. However, puppet manifests do allow you to access both and make decisions based on

Re: [Puppet Users] Custom Facts

On Thu, Sep 1, 2011 at 4:31 PM, Aaron Grewell aaron.grew...@gmail.comwrote: You can't. The whole purpose of facts is to allow Puppet to make decisions based on client data. Variables=server, facts=client. Seriously??? I can edit mcollective's server.cfg file and change the factsource from

Re: [Puppet Users] Custom Facts

Create a variable for server_class in your node definition. On Thu, Sep 1, 2011 at 4:48 PM, Douglas Garstang doug.garst...@gmail.comwrote: On Thu, Sep 1, 2011 at 4:31 PM, Aaron Grewell aaron.grew...@gmail.comwrote: You can't. The whole purpose of facts is to allow Puppet to make decisions

Re: [Puppet Users] Custom Facts

On Thu, Sep 1, 2011 at 4:56 PM, Aaron Grewell aaron.grew...@gmail.comwrote: Create a variable for server_class in your node definition. And then? -- You received this message because you are subscribed to the Google Groups Puppet Users group. To post to this group, send email to

Re: [Puppet Users] Custom Facts

And then assign classes based on that. Standard if logic or case statement as you prefer. On Thu, Sep 1, 2011 at 4:57 PM, Douglas Garstang doug.garst...@gmail.comwrote: On Thu, Sep 1, 2011 at 4:56 PM, Aaron Grewell aaron.grew...@gmail.comwrote: Create a variable for server_class in your node

Re: [Puppet Users] Custom Facts

On Thu, Sep 1, 2011 at 4:58 PM, Aaron Grewell aaron.grew...@gmail.comwrote: And then assign classes based on that. Standard if logic or case statement as you prefer. On Thu, Sep 1, 2011 at 4:57 PM, Douglas Garstang doug.garst...@gmail.comwrote: On Thu, Sep 1, 2011 at 4:56 PM, Aaron

Re: [Puppet Users] Custom Facts

Ah. I don't know how mcollective works so I'm not sure how to address that. If there's a YAML data file involved then you could push it with Puppet... On Thu, Sep 1, 2011 at 5:02 PM, Douglas Garstang doug.garst...@gmail.comwrote: On Thu, Sep 1, 2011 at 4:58 PM, Aaron Grewell

Re: [Puppet Users] Custom Facts

On Thu, Sep 1, 2011 at 5:05 PM, Aaron Grewell aaron.grew...@gmail.comwrote: Ah. I don't know how mcollective works so I'm not sure how to address that. If there's a YAML data file involved then you could push it with Puppet... Yes, mcollective can read a YAML file, which by default is

Re: [Puppet Users] Custom Facts

On Thu, Sep 1, 2011 at 5:02 PM, Douglas Garstang doug.garst...@gmail.comwrote: On Thu, Sep 1, 2011 at 4:58 PM, Aaron Grewell aaron.grew...@gmail.comwrote: And then assign classes based on that. Standard if logic or case statement as you prefer. On Thu, Sep 1, 2011 at 4:57 PM, Douglas

  1   2   >