Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] [EXTERNAL] Re: Adding homegrown tools to perfsonar

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] [EXTERNAL] Re: Adding homegrown tools to perfsonar


Chronological Thread 
  • From: Mark Feit <>
  • To: "Uhl, George D. (GSFC-423.0)[Arctic Slope Technical Services, Inc.]" <>, "" <>, "" <>
  • Subject: Re: [perfsonar-user] [EXTERNAL] Re: Adding homegrown tools to perfsonar
  • Date: Mon, 1 Feb 2021 15:31:47 +0000

Uhl, George D. (GSFC-423.0)[Arctic Slope Technical Services, Inc.] writes:

 

I went ahead and tried to add the TCPping client into the suite of pscheduler tools for RTT.  Using subversion, I downloaded the latest trunk branch of the pscheduler package off github and followed the instructions provided here: https://github.com/perfsonar/pscheduler/tree/master/scripts/PDK. I completed steps #1 and #2 but I’m stuck on #3.  I don’t see anything called “cbic” anywhere in the package.    If I don’t need to do that step, how do I get my tool recognized by pscheduler?

 

There’s a missing step:  The plugin needs to be developed on a system that’s set up for pScheduler development.  (Ed:  That should probably be mentioned in the docs.)  You’re one of a very few people outside the project who’s taken on plugin development, so we’ll use this process to fill in the gaps.

 

The quickest route to that is with Vagrant.  I have a Vagrantfile that builds up a set of CentOS 7 systems that’s properly configured for development:  https://github.com/perfsonar/pscheduler/blob/master/scripts/vagrant/dev-cluster/Vagrantfile.  Do the following:

 

  • Fork pScheduler into to your own GitHub account.
  • Follow the instructions at the top of the Vagrantfile.  You’ll probably want to set the number of machines to 1 unless you need two.
  • Log into the VM as yourself per the instructions.
  • Become root (sudo -i).
  • cd /local/<yourlogin>
  • Clone the forked repository (git clone https://github.com/george/...)
  • cd pscheduler
  • Check out the current production branch (git checkout 4.3.2)
  • make
  • Wait awhile.  When the make finishes, you’ll have a system with a fully-functioning pScheduler (but none of the toolkit’s other ameneties).
  • Go through the development process as outlined in the PDK.  The missing ‘cbic’ is a target in a Makefile template I developed that stands for “clean, build, install, clean” and will compile the plugin into an RPM and install it.

 

If you need some Zoom time to get underway, I have some time over the next few days that’s not spoken for.

 

--Mark

 




Archive powered by MHonArc 2.6.24.

Top of Page