Re: pcp updates: dynamic metrics, pmdapapi, containers, qa

[fche@xxxxxxxxxx (Frank Ch. Eigler)]

> [...]
> Nathan Scott (1):
>       libpcp/pmcd: protocol-level support for containers
> [...]

Can you explain further your intended design for this, so we can get a
chance to review before it gets cast in stone?

What is the exact interpretation of "container name" that is to be
passed?  A path component under the global /sys/fs/cgroup?  Same for
all PMDAs?  Which cgroup manager-type (devices? cpu,*)?  Does that
work with nested containers a la lxc?  What about systemd?  nested
systemd a la atomic/rocket?  libvirt?  Is a process running within a
container namespace required (& able) to know its global container
name in order to get stats for its own cgroup?

(The user interface to the various container tools usuall give a
friendly name, but for pcp purposes, we may well need to canonicalize
them to lower level identifiers for a clear operational purposes.)

- FChE