pcp
[Top] [All Lists]

Re: pcp updates

To: nscott@xxxxxxxxxx
Subject: Re: pcp updates
From: Mark Goodwin <markgw@xxxxxxx>
Date: Wed, 24 Oct 2007 11:57:54 +1000
Cc: kimbrr@xxxxxxx, pcp@xxxxxxxxxxx
In-reply-to: <1193190060.24082.61.camel@edge.yarra.acx>
Organization: SGI Engineering
References: <1193124251.24082.36.camel@edge.yarra.acx> <471E9D69.8030509@sgi.com> <1193190060.24082.61.camel@edge.yarra.acx>
Reply-to: markgw@xxxxxxx
Sender: pcp-bounce@xxxxxxxxxxx
User-agent: Thunderbird 1.5.0.13 (Windows/20070809)


Nathan Scott wrote:
On Wed, 2007-10-24 at 11:18 +1000, Mark Goodwin wrote:
Much of that particular git commit is SGI code (merged into my git
tree).

yes, as Michael already pointed out.

Michael, what's the plan for reconciling this into the master
internal dev tree? A fair bit of review work will be needed,
followed by another round of qa and push to oss.

That is the plan (I'd imagine). Then rinse, repeat, rinse, repeat - as new stuff is incoming all the time.

yeah ok, I'd still like to see some scripts though.

BTW, at some point it'd be good to discuss the libpcp changes for
different contexts with different proxy hosts (and the associated
pmMetricSpec changes you mentioned the other day Mark) - is this
something you guys might look at developing?  Its not going to see
light of day from me for a long time (kmchart eating lots of time),
but the user interface support for that in kmchart is mostly there
and it'd be a _really_ useful feature...

yes, eventually. We have multiple-firewall situations to handle with the new SGI clusters. The high level spec is quite simple: augment the hostname argument to pmNewContext to allow a chain of proxys separated by literal ':'. e.g. pminfo -h proxy_a:proxy_b:targethost then hack pmproxy so it can follow chains. No changes required to any existing apps (other than pmproxy). Not sure how much of this is worth doing since ssh tunnels can achieve the same thing, albeit a lot less conveniently, but with better security options.

For the metricSpec changes: support for the proxy: syntax in the host
component, and regex in the metric and optional instance components.

Thanks
-- Mark

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