Puppet users - Oct 2008 - puppet, facter and non-scalar values (2nd attempt)

I wrote a mail a few days ago not to get any answers so I''ll
try and reformulate the question in different terms.

I need to collect several related "facts" on a server for later use
within puppet. These "facts" are related.  The puppet documentation
seems to imply that the correct way to make puppet aware of new facts
is to adapt facter and make it aware of these new custom facts.

That seems fine but it also seems that all facter facts are single scalar
values which does not fit cleanly with what I am trying to do.

MUST facter facts be single scalar values which can be evaluated as
such by $variable from within puppet?

I''m running puppet on Linux and I want to store volume group names (the
first column output of /usr/sbin/vgs) but also within each volume group
the list of logical volumes (partitions, output of /usr/sbin/lvs) each one
contains. I can think of other non-scalar values which it might be nice to
use such as network interface names, and ip addresses of each interface.

If these values are currently not known to puppet what''s the best way
of obtaining them so they can be used within the puppet configuration
to configure other aspects of the system?  Is it ok to somehow directly
interface to Ruby to do this and if so how''s this best done?

Thanks for pointers and suggestions.

Simon

--~--~---------~--~----~------------~-------~--~----~
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 group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---