similar to: List of Facter "facts"

Hi there, The links to the documentation of Puppet in the right side of the page seems to be ordered alphabetically, I find confusing to access the documentation using the current menu. I think it would make sense to order them according to some "natural" order for reading it. I mean, maybe it should be something like Index, Introduction, Installation, Language Tutorial... Best regards

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 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

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

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

I have successfully updated puppet clients from my master using the built-in WEBrick server. When I updated my setup to using Apache2+passenger, my clients get this error message: err: Could not retrieve catalog from remote server: Error 400 on SERVER: You cannot save facts to the code store; it is only used for getting facts from Facter warning: Not using cache on failed catalog err: Could not

I can''t seem to find anyplace that list the facts that I can us in my puppet scripts; can somebody please point me in the right direction? -- -- Perfection is just a word I use occasionally with mustard. --Atom Powers--

Hi, I need to remove a custom fact from facter. How to do this? For now, I set the environment variable FACTER_customfact = something but would like to get rid of it permanently. Thanks, Werner -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this

Hi all, first post here... reposting this from Stack Overflow as it didn''t get much traction there... I am using puppet to read a fact from facter, and based on that I apply a different configuration to my modules. Problem: the puppet agent isn''t seeing this fact. Running puppet agent --test interactively works as expected. Even running it non-interactively from a script

Hi all, I''m looking at changing the operatingsystemrelease fact for Red Hat. Linux currently just uses the kernel release as the operating system release, but I''ve got a client who wants the release to have both the specific distro (e.g., AS or EL) and the release (e.g., 3 or 4). Will this particularly annoy anyone? Anyone want to help make the release string work on

Hi all, Jennifer Davis from BayLISA has done us the service of already posting the presentation from this past Wednesday night: http://video.google.com/videoplay?docid=8202036065161263530&hl=en http://video.google.com/videoplay?docid=7740462681265962824&hl=en It''s about 2 hours total, and I can''t promise it''s any kind of amazing presentation, but I do a

Hi, We are trying to use a custom fact to tell us the version of our service in order to do hot deployment. The idea is that we poll mco for servers with this fact matching the new version until it returns that there are some, which is a signal we can move on to the next server. Unfortunately we''re bumping into the cache of facts mentioned in the server config here:

Hi, I''m following http://reductivelabs.com/trac/puppet/wiki/PluginsInModules in order to use a custom fact. My modules looks like: # ls manifests/modules/network/ manifests plugins # ls manifests/modules/network/plugins/facter/primaryint.rb manifests/modules/network/plugins/facter/primaryint.rb as is said in doc. Then: Turn on pluginsync and specify factpath, so that the facts

int he example below I run facter looking for the fact "sp_serial_number". as you can see, the command facter sp_serial_number returns nothing, but the fact is there and is returned when just running facter and grepping for the fact. Some fact seem to work and others do not. any ideas? marcuspro:~ allan$ facter --version 1.5.7 marcuspro:~ allan$ facter sp_serial_number marcuspro:~

Hi, I run into problems with the ipaddress fact using the latest Facter gem (1.6.4, 1.6.5) on SLES11. The versions and gems I use work perfectly fine on SLES10 SP3. The problem: running "facter" without arguments results in an error, even though the erroring fact "ipaddress" is ok. test:~ # cat /etc/SuSE-release SUSE Linux Enterprise Server 11 (x86_64) VERSION = 11 PATCHLEVEL

I see the instructions for creating custom facter recipes here: http://projects.reductivelabs.com/projects/puppet/wiki/Adding_Facts and in this thread, James Turnbull suggests that Facter might some day support other languages besides ruby: http://groups.google.com/group/puppet-users/browse_thread/thread/8c127ae8898d3bcf/c5ca551b77c4eb67?lnk=gst&q=facter+perl#c5ca551b77c4eb67 He writes: