[csw-maintainers] [csw-buildfarm] Fwd: OpenCSW catalog update report (ganglia)

[Daniel Pocock]

On 28/11/11 21:22, Dagobert Michelsen wrote:
> Hi Daniel,
> 
> Am 28.11.2011 um 14:14 schrieb Daniel Pocock:
>>>> 3. be aware the this gmond version doesn't run on a non-global zone
>>>>
>>>> http://bugzilla.ganglia.info/cgi-bin/bugzilla/show_bug.cgi?id=100
>>>
>>> If course the webserver runs in a non-global zone :-P
>>> Could you please apply Brians patch as cited in the patch report?
>>>
>>
>> There are comments in the bug report suggesting the patch may cause
>> gmond not to work in a global zone, so I'm not sure if the patch is ideal
>>
>> I'll have to find a quick way to test if running in a zone or not
> 
> Comment #19 reads ok for me:
> 
>   "Just meet this issue in a Solaris zone. I compiled a small test with Brian's
>    fix. And I found it works great, both in a non-global zone and global zone."

http://bugzilla.ganglia.info/cgi-bin/bugzilla/show_bug.cgi?id=100#c3

   'The problem with the "simple" solution is that it breaks normal
(non-zone)
setups.

 e.g. the following is from a Solaris-10 HA configuration:......'


sounds a bit ominous to me.

At the very least, Ganglia 3.1 series might be able to just refuse to
run in a zone, display a more meaningful error than `ioctl failed' or
just disable this code in a zone or some other `safe' hack, and then
comprehensive zone support can be introduced through trunk

I don't know enough about zones, HA setups and other permutations to say
the ideal way to address the issue

However, another issue that does come to mind: if someone runs gmond in
a zone, is it meaningful to report all of the CPU stats for every zone?
 Or is the CPU inside a zone not really measurable in the same way as a
physical CPU in the global zone?