perfSONAR User Q&A and Other Discussion

[Mark Feit <>]

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

 

Not only was I thinking of a smaller footprint I was also looking at standing up instances of pScheduler/pS4.0 at remote sites on other people’s hosts that hopefully wouldn’t require intervention on their part.  I’ve been looking at Docker as a possible solution.  I’ve been able to build a container that runs bwctld and owampd but I wanted to enable pScheduler as well.  I’ve been following Brian Tierney’s development efforts to build a pS4.0 testpoint container which is still a work in progress.

 

 

DISCLAIMER:  None of what’s described below is supported.  Use it at your own risk for your own entertainment.  :-)

 

I have a pScheduler-only container that I use for some kinds of testing and demos.  You can run all tests between the containers and most tests to off-host pSchedulers.  Running tests inbound is a sticky point that hasn’t been worked out yet.  Brian’s come closer to it than I have, but I don’t really have the cycles to spend a lot of time on it.

 

The container has everything pScheduler needs to run, including a PostgreSQL server, so it’s 100% load-and-go.

 

The scripts and Dockerfile are in with the pScheduler sources at https://github.com/perfsonar/pscheduler/tree/master/scripts/docker.  It only works with CentOS 6 and builds all of pScheduler from source instead of using the repos, but it does get the job done.  You can do the whole build in one step on anything that supports Docker by following these instructions:  https://github.com/perfsonar/pscheduler/wiki/Docker-Notes.  There are also some instructions on how to use the demo script to start a 3-node cluster of pSchedulers on a machine with Docker:  https://github.com/perfsonar/pscheduler/wiki/Docker-Local-Demo.

 

The demo script downloads the container from DockerHub, which is built infrequently.  I just did a build and push with the current code if you want to try it out.

 

--Mark