Date: Wed, 14 Apr 2010 08:02:22 +1000 (EST)
From: Nathan Scott <nathans@aconex.com>
To: kenj@internode.on.net
Cc: pcp <pcp@oss.sgi.com>
Message-ID: <378220262.614601271196142712.JavaMail.root@mail-au.aconex.com>
In-Reply-To: <1271191628.24244.205.camel@bozo.localdomain>
Subject: Re: Local context vs dynamic namespace
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


----- "Ken McDonell" <kenj@internode.on.net> wrote:

> Nathan,
> 
> I know you don't particularly like the environment variable approach,
> but following the $PCP_DERIVED_CONFIG example, we could introduce
> $PCP_LOCAL_CONFIG that might specify the name of a file (perhaps
> stashed
> in $HOME/.pcp at the user's discretion) that contained local PMDA
> specifications (in the syntax for __pmSpecLocalPMDA that was recently
> created).
> 
> So in your case, the file might contain
> 
> clear
> add,60,linux/pmda_linux,linux_init
> add,70,mmv/pmda_mmv,mmv_init
> add,123,aconex/pmda_aconex,aconex_init
> 
> or indeed, simply take the default and add the aconex PMDA, as in
> 
> add,123,aconex/pmda_aconex,aconex_init
> 
> In some ways this is less ugly than the -K stuff for cases where the
> set
> of PMDAs you'd like to be available for PM_CONTEXT_LOCAL is
> non-standard
> and fixed.
> 
> Thoughts?

I was thinking something along those lines, but more system-wide than
user specific.  If we had a /etc/pcp.local.d/ directory, we could have
the agent Install scripts drop a file in there in __pmSpecLocalPMDA
format for dso agents, and we could ship a kernel and mmv one in there
by default.

Infiniband rpm installs could then drop one in there, and the cluster
PMDA would be simplified a bit.

We could also do away completely with dsotab in libpcp then... and
fill that in "on the fly" based on contents of that directory.

cheers.

-- 
Nathan