I'm guessing this isn't the variety of feedback you're looking for,
but just in case:

We recently upgraded a couple of machines from facter 1.3.x to facter
1.5.x and were very dismayed to learn that $operatingsystemrelease on
Solaris had changed from the consistent-with-other-operatingsystems
"5.9" to "9_u8". This made us wonder if we'd need a different version
for every Solaris update (assuming "u8" is update 8, I really have no
idea what it means.)  On RHEL and HP-UX $operatingsystemrelease didn't
change and is what we'd expect (as "5.9" was what we'd expect.)

I haven't taken the time to find the checkin that changed it and read
the justification, perhaps it's the best thing ever, but it threw us
for a loop and broke a lot of branches. Are there Solaris people who
are really in need of that level of detail? You really treat u7
differently than u8?

Perhaps our approach is also the problem... we run RHEL4 and 5, HP-UX
11.11 and soon 11.31 and Solaris 9 and 10. Across these OSes,
$operatingsystemrelease made sense to us (as the numbers in the
previous sentence) moreso than say $kernelversion because on RHEL we
don't necessarily have the same kernel running everywhere (or want to
depend on that) but we do have things we want to do on RHEL4 vs 5 so
branching on $kernelversion doesn't really work in the way we'd been
branching on $operatingsystemrelease.

I too love the idea of a facter.d that can run scripts/bins in
whatever language. I hope that the location of that directory won't be
hard-wired. The difficult part of this then becomes the namespacing of
these facts and/or returning multiple facts from the same script.

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

Reply via email to