This relates to a discussion we are having in the Redmine ticket
I am extending the processorcount, physicalprocessorcount and processorX
facts that exist for Linux and Solaris.
I personally find the behaviour of the processor facts on Solaris
myhost# facter |grep proc
physicalprocessorcount => 1
processor0 => SPARC64-VII
processor1 => SPARC64-VII
processor2 => SPARC64-VII
processor3 => SPARC64-VII
processor4 => SPARC64-VII
processor5 => SPARC64-VII
processor6 => SPARC64-VII
processor7 => SPARC64-VII
processorcount => 4
We can see that physicalprocessorcount is returning the number of physical
CPUs which is good, the processorX array is getting populated with virtual
CPUs, and processorcount is returning the number of cores. The command
used to set processorcount is essentially kstat cpu_info |grep core_id
sort -u.However, I suspect Solaris sysadmins are more familiar with using commands
like psrinfo, prtdiag, and mpstat to get CPU count, and these all report
the number of CPUs as 8 rather than 4.
If I was writing this from scratch I would have a fact called something
like ProcessorCoreCount and have that report 4 and then a separate fact
ProcessorCount that would report 8 - as psrinfo is doing.
Therefore I am interested to know if others out there regard this behaviour
as a 'bug or feature', and also get some feedback on how people are using
these facts out there.
Thanks in advance.
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/WlRmUVNCey4J.
To post to this group, send email to email@example.com.
To unsubscribe from this group, send email to firstname.lastname@example.org.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.