This is for Henry. I've built a pcp-webd container image and
it seems to run just fine serving the pcp webapi REST API,
see pmwebapi(3) and pmwebd(1). I ran it on my local system, which
has regular pmcd already running, but it could alternatively be
used with the pcp-collector container instead.
Also, Nathan and I will be discussing container QA strategies next
week whilst at LCA. Until then, QA is a manual process, e.g. to
test this container just point a browser at your host (myhost) :
http://myhost:44323/pmapi/context?hostname=localhost
This should return a context that can be used in subsequent requests
(see pmwebapi(3) for details).
Changes committed to git://git.pcp.io/mgoodwin/pcp master
commit 539ea77b48a12e19f658fbc3c247d1517c7d2a50
Author: Mark Goodwin <mgoodwin@xxxxxxxxxx>
Date: Wed Jan 27 14:44:39 2016 +1100
containers: add pcp-pmwebd container to serve pcp-webapi requests.
This adds a pcp-pmwebd container. It needs a local pmcd service,
which can be provided either by a regular local pmcd on the host
_or_ by a running pcp-collector container. It listens on the default
pmwebd port (44323 by default). This can be changed by editing
pmwed.options in the container.
Host platforms that don't have an active avahi service will need
to add the new pmwebd -S flag in the pmwebd.options file in the
container to disable service advertising (see Nathan's follow-up
commit for this).
modified: build/containers/GNUmakefile
new file: build/containers/pcp-pmwebd/Dockerfile
new file: build/containers/pcp-pmwebd/GNUmakefile
|