How about creating a processorcorecount and processorthreadcount with
"correct" meanings? That then leaves the option to deprecate
processorcount.
I've realised that at some point in the past I have created a
processorthreadcount fact because I needed a consistent source of this
information on bot
;
>
> I'm inclined toward the second option.
>
> On Monday, December 3, 2012 2:39:33 AM UTC-8, Andrew Beresford wrote:
>>
>> I have set up puppet to create a facts.yaml file for mcollective using
>> the following line:
>>
>> content =
49 PM UTC+11, Andrew Beresford wrote:
>>
>> Feature :)
>
>
> I do understand what the code is doing but question whether that's what it
> should be doing. While it's ultimately a matter of opinion, it violates
> the 'principle of least surprise'
Feature :)
This all comes down to the architecture of your processor.
Your SPARC64-VII processors is a quad-core, two-way SMT processor. So, you
have one physical CPU, four cores, and 8 threads.
physicalprocessorcount is derived from the output of psrinfo -p
and processorcount is derived fr
I have set up puppet to create a facts.yaml file for mcollective using the
following line:
content => inline_template("<%= scope.to_hash.reject { |k,v| k.to_s =~
/(uptime.*|timestamp|.*free|macaddress.*|ipaddress)/ }.to_yaml %>"),
However, it is creating a lot of unnecessary changes by reord
