pcp
[Top] [All Lists]

Re: [pcp] pcp updates: pmmgr, pmwebd

To: Mark Goodwin <mgoodwin@xxxxxxxxxx>
Subject: Re: [pcp] pcp updates: pmmgr, pmwebd
From: "Frank Ch. Eigler" <fche@xxxxxxxxxx>
Date: Tue, 28 Apr 2015 07:06:24 -0400
Cc: pcp <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <553F4BA8.5000001@xxxxxxxxxx>
References: <20150421224405.GN6822@xxxxxxxxxx> <5536E65F.50600@xxxxxxxxxx> <20150422000949.GP6822@xxxxxxxxxx> <553F4BA8.5000001@xxxxxxxxxx>
User-agent: Mutt/1.4.2.2i
Hi -

> Howdy Frank, will I just pull in all your changes? Or cherry-pick
> only the pmwebd changes? Your tree of unmerged stuff seems to go
> back to the commit listed below I think.

I'd love for both braches to be reviewed & merged.

> The pmmgr changes are marked as 'blocked' on
> https://trello.com/b/5t9Ml341/release-task-tracking.

That one is private (why?).  Also, I thought y'all had switched to a
Libreboard setup.

Anyway, the pmmgr changes shouldn't be so marked.  That code works,
includes docs & qa.  It is not on by default, so is harmless despite
the infrastructure bugs.  Yet it is possible to use the code, for
example to simply track container lifetimes, if there exists even one
pcp metric (pmcd.hostname?) that is reliably fetchable from within a
&container=FOO connection.  And surely there exists at least one such
metric.


- FChE

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