pcp
[Top] [All Lists]

Re: [pcp] Local context vs dynamic namespace

To: Nathan Scott <nathans@xxxxxxxxxx>
Subject: Re: [pcp] Local context vs dynamic namespace
From: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Wed, 14 Apr 2010 11:45:49 +1000
Cc: pcp <pcp@xxxxxxxxxxx>
In-reply-to: <1271199338.24244.278.camel@xxxxxxxxxxxxxxxx>
References: <378220262.614601271196142712.JavaMail.root@xxxxxxxxxxxxxxxxxx> <1271199338.24244.278.camel@xxxxxxxxxxxxxxxx>
Reply-to: kenj@xxxxxxxxxxxxxxxx
Just to go in circles once more ... PM_CONTEXT_LOCAL is only ever going
to work for the (DSO) PMDAs that have been "Install"ed on the local host
because this is the only way to get the correct PMNS installed as well.

So I think the using pmcd.conf model would work just fine ... and
Nathan's right we don't need to extend the pmcd.conf format -- if you
are a DSO PMDA defined in pmcd.conf then by default you're available via
PM_CONTEXT_LOCAL, end of story.

On Wed, 2010-04-14 at 08:55 +1000, Ken McDonell wrote:
> ...
> 6. With all of this, it is not clear how useful the CLEAR operation to
> __pmLocalPMDA will be ... I can still see a remote case for needing ADD
> and DEL, but in some ways the need for all of __pmLocalPMDA and
> __pmSpecLocalPMDA would almost go away if the PMDAs for PM_CONTEXT_LOCAL
> was driven off pmcd.conf ... except for your original requirement 8^(>
> to be able to use metrics from a PMDA when pmcd was not running ... if
> pmcd is not running then perhaps the PMDAs have not been Installed and
> pmcd.conf contains no reference to the PMDAs of interest.
> 
> I think I've argued around a full circle so, probably scrap 5. and 6.
> and go with the rest of the suggestion.

<Prev in Thread] Current Thread [Next in Thread>