Hello,
We are currently evaluating Puppet and Chef on several criteria and we
have found a big difference between the amount of information
retrieved by Facter in Puppet and the amount of information retrieved
by Ohai in Chef for a same virtual machine.
There is about 2000 lines in the JSON file
Christophe,
Let me ask a question: what extra information is Ohai providing (that
Facter does not currently) that you would be using in your
manifests/cookbooks? Usually people utilize similar bits of
Facter-provided information (operatingsystem, release version, ipaddress,
interfaces, domain,
Hello Gary,
Thank you for your answer.
First, I should have written about raw meaningful data rather than raw
useful data because you are right that a lot of the extra information are
not actually useful :)
For information, the aim is not to use the information in modules, but to
fill a CMDB
Hi Christophe,
The facter tag is something a user would have to use when they release
their module. There are many more custom facts on the Forge that
simply aren't tagged. Your thread inspired me to create a feature
request for searching specifically for facts:
On Friday, May 11, 2012 11:42:52 AM UTC-7, Ryan Coleman wrote:
Hi Christophe,
The facter tag is something a user would have to use when they release
their module. There are many more custom facts on the Forge that
simply aren't tagged.
Given that the current module definitions
On Fri, May 11, 2012 at 12:58 PM, Philip Brown p...@bolthole.com wrote:
Given that the current module definitions require known locations for factor
extensions, I find this a bit odd.
How about making the uploader autotag 'facter' any module that has files
under lib/facter ?
That's precisely
Christophe,
I would suggest not using Puppet or Chef to pass data around
constantly that isn't going to be used by your actual code. Instead,
you might want to set up a proper SNMP infrastructure such that you
can get all of the information that you want and poll your network
devices, etc... with
