perfSONAR User Q&A and Other Discussion

["Uhl, George D. (GSFC-423.0)[SGT INC]" <>]

Andy,

I’ve been following Brian Tierney’s development efforts to build a pS4.0 testpoint docker container and he’s run into some issues with initializing postgress.  I’ve been able to create a docker container that runs bwctld/owampd which is fine for now but I will  also look into other options for standing up a lightweight pS4.0 testpoint node.

Thanks,

George

From: Andrew Lake <>
Date: Monday, February 13, 2017 at 2:47 PM
To: "" <>, George Uhl <>, Mark Feit <>
Subject: Re: [perfsonar-user] pScheduler and postgres

Hi,

One point of clarification too, if you install just the perfsonar-tools package you will get just the pscheduler command-line clients that allow you to run essentially third party tests from that host via the command-line. No postgresql, but you won’t be able to use that host as an endpoint of a throughput test, reverse traceroute or reverse ping test all of which need full blown pscheduler on the host. You’ll likely want the perfsonar-testpoint bundle which gives you a full pscheduler install including postgresql.

Thanks,

Andy 

On February 13, 2017 at 2:33:18 PM, Mark Feit () wrote:

Uhl, George D. (GSFC-423.0)[SGT INC] writes:

 

Does pScheduler require postgres to function if it’s installed as part of the perfsonar-tools package?

Yes, it does.  All of the persistent data storage and many of the processing functions are done in the database.  Taking that route cut development time considerably and gave us a lot of sophistication, reliability and integrity we wouldn’t have had with hand-rolled code.

 

The footprint isn’t very big.  All of the development was done in an environment much smaller than our minimum recommended configuration, and its use of resources has been watched carefully.

 

If you’re concerned about security, no use of PostgreSQL leaves the host and the pScheduler database is configured not to accept connections from anywhere other than locally.  Authentication is done with a long, random password that’s unique to every installation, changed whenever the software is updated and stashed away in a place where the few processes that need it can see it.

 

HTH.

 

--Mark