pcp
[Top] [All Lists]

Re: PCP-monitor container

To: henry c <hc3249@xxxxxxxxx>, Nathan Scott <nathans@xxxxxxxxxx>
Subject: Re: PCP-monitor container
From: Mark Goodwin <mgoodwin@xxxxxxxxxx>
Date: Tue, 9 Feb 2016 13:00:32 +1100
Cc: pcp <pcp@xxxxxxxxxxx>
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <CABMF9cuWknRXdrMyEFqgeyetD23c6suvv3_bhpo=83EsMcptfg@xxxxxxxxxxxxxx>
References: <CABMF9cuWknRXdrMyEFqgeyetD23c6suvv3_bhpo=83EsMcptfg@xxxxxxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
On 02/09/2016 12:00 PM, henry c wrote:
Nathan & Mark,

We were able to get pcp running in the containers.

Thanks for your contribution to this!

However during trial and process, we discovered that even without pcp-monitor 
the pmwebd api is working as expected.

The pmwebd and associated web apps and infrastructure is shipped in the 
pcp-webapi package.


We just want to make sure that we are not missing and that pcp-monitor is not 
actually needed.

correct - pcp-monitor is not required; the pcp-webapi package will also install 
the
required dependencies. The pcp-monitor package is just a pseudo RPM that has no 
files itself,
it only has dependencies on all the various pcp monitor bits, one of which is 
pcp-webapi.

You will need pmcd running on the host that you want to run pmwebd on. This can 
be provided
either by installing the pcp-collector package (or just the pcp package is 
enough) and
enable and start the 'pmcd' service, _or_ you can deploy the pcp-collector 
container to
provide the pmcd service. Once the pmcd service is enabled and running, you can 
then
deploy the pcp-pmwebd container.

Now that pcp-3.11.0-1 has been moved to stable in Fedora f23, f22 and f20, I 
have re-built
the PCP container images to use the stock pcp packages from fedora:latest, and 
pushed the
resulting container images to bintray. You can deploy these containers without 
installing
anything, just pull and run the containers as follows (as root, with docker 
service enabled) :

# docker pull pcp-docker-containers.bintray.io/pcp-collector:latest
# atomic run pcp-docker-containers.bintray.io/pcp-collector:latest

# docker pull pcp-docker-containers.bintray.io/pcp-pmwebd:latest
# atomic run pcp-docker-containers.bintray.io/pcp-pmwebd:latest

Both of the above are layered on the pcp-base container image, which is itself 
layered
on the fedora:latest base image, currently f23 based.

Once the containers are deployed, point your browser to http://MYHOST:44323  
(for host MYHOST).
You may need to open ports 44323 and the 'pmcd' service on MYHOST's firewall

If you don't have the 'atomic' command, then the deployment instructions are a 
bit more
complicated - use the script in build/containers/scripts/pcp-docker-run instead 
of the
'atomic' command.

Regards
-- Mark

<Prev in Thread] Current Thread [Next in Thread>
  • Re: PCP-monitor container, Mark Goodwin <=