Re: zeroconf subrpm package

On Mon, Oct 24, 2016 at 1:50 PM, Nathan Scott <[email protected]> wrote:

>
>
> ----- Original Message -----
> > [...]
> > > ISTM that the pcp-collector subrpm varies from this one only in that
> > > the pcp-collector Requires: all the pmdas.  How about
> > > repurposing/renaming that subrpm to a "pcp-pmdas-all" (like is done
> > > elsewhere in fedora),
>
> We can't change the definition of pcp-collector like this - its been
> released already, people will have it installed and on upgrade there
> are very specific changes the pcp-support-zeroconf package will make.
> Those changes will be inappropriate for some existing installations.
>
> A Provides: pcp-pmdas-all on the existing pcp-collector package would
> be fine, not sure if thats really useful though.
>
> > We could also change the pmlogger config to log more frequenty with a
> > different set of metrics.
>
> Yes, thats one of the pcp-support-zeroconf needs Mark has, AIUI - proc
> and xfs.perdev will become enabled by this package.
>
>
>
[Sorry for the delay in responding here]

The rationale for 'pcp-support-zeroconf' is to minimize the manual
configuration steps needed to collect useful performance data for off-site
support and analysis purposes, in typical enterprise production
environments. Installing the package (either directly or via a 3rd party
packaging dependency) would configure something like the following
automatically via a %postin scriptlet (or the equivalent for non RPM
platforms) :
- set the default logging interval to 10s
- enable xfs.perdev logging
- enable some optional PMDAs and logging thereof
- enable atop-proc logging (and maybe more proc metrics too) at 30s
- only allow local pmcd connections (or maybe even no pmcd at all and only
enable the pmlogger service in local mode - but that's currently limited to
certain DSO PMDAs only)
- disable all inet domain sockets, only listen on unix domain or local
pipes etc
- enable and start the pmlogger and pmie services (and maybe pmcd too if
local pmlogger is insufficient)

Obviously there are logistical issues with this, e.g. what if pcp is
already installed and configured, handling upgrades, etc., and there are
probably policy issues too (though enabling and starting services might be
OK if daemons only listen locally).

Anyway, that's my wish list - let's discuss!

Regards
-- Mark