similar to: Where are Facter facts?

Does any one have a recipe for getting facter facts from ldap?

Hello! I''ve been trying to use facts from Facter in a custom function. I''ve been following Matthew''s entry in the wiki (http://www.reductivelabs.com/trac/puppet/wiki/WritingYourOwnFunctions). What i''m seeing is that Facter[''fqdn''].value is always returning the fqdn of the puppetmaster host. I was expecting the fqdn of the client host.

Hello dear list. First of all thanks to all the developers for the great work on puppet. After using it for a while, there is not better tool to manage a network! I have a problem with the $processor fact, which seems to be either not there or ignored at all. I try to implement package deployment for the Macs (Intel vs. PowerPC) as described here:

Hi, I''m new to Puppet, but it looks very good, so far. We are going to use it for a multi-tier (DEV, QA, staging, production) environment which is consists of web, app, and database servers. I have a couple of suggestions for the Puppet documentation that may save others some time. First, it seems node names MUST be FQDNs (hostname and hostname. will not work). Since we are not using

Hi, In our dev/int environemnts, our user base wants to be able to change managed files at will during the day but be notified via email of changes that happen. At night they want the files replaced to their known good state if there were changed. I tried to do this with a custom function that wraps two file types, one that just watches checksum, the other that does a reset of content with a

I''m, still, working on converting my cfengine configs into puppet; one of the major hang-ups is the lack of any find/replace in puppet. So for those of you who are using FreeBSD and puppet, how do you manage you rc.conf? -- -- Perfection is just a word I use occasionally with mustard. --Atom Powers--

I have a lot of this going on: -- class lighttpd { import "lighttpd.pp" } class mysql { import "mysql.pp" } class nagios { import "nagios.pp" } class netdisco { import "netdisco.pp" } class nfs_server { import "nfs.pp"} class openldap { import "openldap.pp" } -- But my client is trying to realize all of these, even though I

I have been working on adding some predicate functions to puppetlabs-stdlib that test things based on ''interfaces'' and related facts. The functions themselves seem to work fine in my manifest-based smoketests, but I am running into trouble that may or may not be due to my ignorance about rspec or Facter. Something needs to be done to initialize Facter because

[This email is either empty or too large to be displayed at this time]

I''m getting certificate errors when I attempt to run puppetd on the puppetmaster. As near as I can tell, this is because I''m using the same puppet.conf for both puppetd and puppetmasterd; but puppetmaster runs as user "puppet" and puppetd runs as user "root", yet both expect the certificates to be readable and chmod 600. I tried telling puppetd to use

Facter has the feature that it will turn any environment variable named FACTER_* into a fact. I can do this on the commandline no problem, but when I attempt this in puppet it seems to ignore that parts. Is anyone else seeing this? (Is this expected behavior?) I don''t see a ticket or a mail thread on it - though my searching powers have been weak the last couple of weeks... Thanks,

Quick and dirty: --- lib/facter.rb (revision 203) +++ lib/facter.rb (working copy) @@ -989,6 +989,18 @@ %x{/usr/sbin/scutil --get LocalHostName} end end + Facter.add(:interfaces) do + confine :kernel => :linux + setcode do + %x{/sbin/ifconfig -a -s}.split($/)[1..-1].collect {|line|

I''m trying to load custom facts via /etc/facter/facts.d/* according to instructions on http://docs.puppetlabs.com/guides/custom_facts.html#structured-data-facts I must have missed a setting somewhere because I get nothing. The first clue may be that /etc/facter didn''t exist. I had to create it manually. Is there a setting or search path I need to create? Details: puppet

We found out, the hard way, that version 1.7 of Facter adds facts for mounted linux file systems. This is nice for normal servers. For a server hosting Oracle not so good. We went from about 100 facts per server to well over 3,000 (our Oracle boxes have quite a few volumes mounted). Of course, this choked our ENC (Foreman) having this many facts pumped into it and required us to downgrade

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 "Puppet Users" group. To post to this group, send email to

Hi everyone, I have a fact which looks like that: drbdconnectionstate0. You see the "0" at the end... Now I''d like to access this fact in a "dynamic" way, the "0" should be variable. I''m thinking of something like that: if ${drbdconnectionstate0}${drbddevice} == ''Unconfigured''. But as you may guess, this does not work... Has

Hi. I have the following facts available: # facter | grep oper operatingsystem => CentOS operatingsystemrelease => 6.2 Now, if I wish to use conditionals on these facts, I have to do it like this: case $operatingsystem {} case $::operatingsystemrelease {} I''m puzzled as to why can''t I just use $operatingsystemrelease, and what do these two semicolons mean? Thank

Hi All Background: I am running Puppet to configure ESX 3.5 servers by NFS mounting the Puppet binaries and configuration from a shared server. This is to ensure VMware don''t come back refusing support for installing non standard software on the server. # ruby -v ruby 1.8.7 (2009-04-08 patchlevel 160) [i686-linux] # facter -v 1.5.5

file. I don''t know why it will work for other hosts but these steps do not work for this.. there are no extra outputs from using --debug On 4/9/07, Atom Powers <atom.powers at gmail.com> wrote: > > On 4/9/07, Mike Zupan <hijinks at gmail.com> wrote: > > I recently had a working puppet server serving around 4-5 clients. One > of > > the clients needed to

Hi, I''ve noticed that defining multiple facts in one file is possible, and puppet can make use of them correctly, but when trying to call with facter --puppet they are not shown, do I need something special to make them work as any other single custom fact? Master is running 2.6.7 This is a custom fact with two facts in it: [modules/foobar/lib/facter/foobar.rb ] require