pcp
[Top] [All Lists]

Re: [pcp] JSON PMDA

To: Nathan Scott <nathans@xxxxxxxxxx>
Subject: Re: [pcp] JSON PMDA
From: David Smith <dsmith@xxxxxxxxxx>
Date: Tue, 05 May 2015 16:16:40 -0500
Cc: pcp <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <1344441557.4430503.1429658863072.JavaMail.zimbra@xxxxxxxxxx>
References: <54F9F92D.4010202@xxxxxxxxxx> <448002717.7934024.1427683964254.JavaMail.zimbra@xxxxxxxxxx> <552699FE.7040801@xxxxxxxxxx> <2139482617.15593599.1428634701360.JavaMail.zimbra@xxxxxxxxxx> <552D6524.1030803@xxxxxxxxxx> <1237712965.18667183.1429054767135.JavaMail.zimbra@xxxxxxxxxx> <5536C228.8010001@xxxxxxxxxx> <1344441557.4430503.1429658863072.JavaMail.zimbra@xxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
On 04/21/2015 06:27 PM, Nathan Scott wrote:
> Hi David,

... stuff deleted ...

> As per the earlier mail with kenj (re ioctl), I think the only new API we
> will need for this aspect would be something like:
> 
> int pmdaCacheResize(pmInDom indom, int maximum);
> 
> the rest of the pmdaCacheOp(3) interfaces should give us the rest of the
> cache manipulation functionality you need (like persisting, restoring, &
> so on).

OK, here's a quite rough patch that makes the needed changes to cache.c
(and associated files), and then modifies the JSON PMDA to use indom
caches for cluster and metric assignments. There are several "FIXME"
comments scattered throughout the changes, and more code will need to be
added to pmda.py to make this more user-friendly. But, it does seem to
work in the limited testing I've done.

-- 
David Smith
dsmith@xxxxxxxxxx
Red Hat
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)

Attachment: cache_change.patch
Description: Text Data

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