Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] Custom tool for tests

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] Custom tool for tests


Chronological Thread 
    < Chronological >      < Thread >
  • From: Mark Feit <>
  • To: Fabio Andrijauskas <>, "" <>
  • Subject: Re: [perfsonar-user] Custom tool for tests
  • Date: Wed, 18 Jan 2023 01:06:46 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=internet2.edu; dmarc=pass action=none header.from=internet2.edu; dkim=pass header.d=internet2.edu; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=ZPGMqdLhgPPvhj6FP3pWQWGvPX2n95CRA23ISUWeYOE=; b=FFscIjLkacFOdOP1YNmthhcj2bd+1bvMGjkFHAnIEkCuNub/8AJCFPeelh3YvAvrVBHA9Hf4gpRcKcJ6IjeiT98CzdgCRJQuR065ntpQ+N3cmVFGwPzHBuD4j9Ak57guknnxYgp4xvH7MEWZ6fMC5SB1GlwU5lD1Y65wyJqa5RkXpgGFIsGwsuJc05l7rJL5NnVdwKuZZ6knm6kSc6FaIIHPjNWp+BPDtOZu9jFHMtSENNhlrR88OKzbcR/+pMhGly5gp09JfdCGSLixYflPGZ4UMMnyZ078eH8VYrSXsdg8AEAxGwOyMrbvUiD5qGMQMy0P6yGB+7EecMRRsc4+Kg==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=GXOVQQVBwmRBQO+CHKuR6gnC4Bt2haB/ddxZImyAK3j1tH5z2jY2VD8NbErTK+p08hj8XYul/26KGXqJFSX49ZliJPR5WerGLV5x8WqxFDU3ua9/pNPAgKj11PTdq4GIinEXULzwlFl9cK5Ev5agnR1chO2apAIczhngB1tWRYhJUZM4rTCO0tEBHAB0ZvuCxtfy48NkRYzuna4LrwkPnr+aGV0CEEPDKYW0Bud7lIqmQbPI0zcaY4ubm+EuzrzN26kSKiGF67BTd3q+3wSLBgpPctMU6Xlj+Cv0z/aGfgAeKKFMdKv/yqsdeIUK756gAaKgDA+6oWW6/uBwEg4zjQ==

Fabio Andrijauskas writes:

 

Is there an "easy" way to add a new tool on the perfosnar-testpoint?

 

Easy is a relative term.  pScheduler, which is the part of perfSONAR that carries out the measurements, has a plugin-based architecture that makes extending it fairly straightforward once you understand the concepts behind how it works.  The process does require developing code and we have a library of functions that streamlines a the common parts.  BWCTL, pScheduler’s predecessor, was so difficult to extend that it was rarely done.

 

There is a program available within the pScheduler sources called the Plugin Development Kit (PDK) that can provide skeletal versions of test, tool and archiver plugins.  Within those skeletons is guidance about what order to build things.

 

If you can elaborate on what you’re interested in doing, I can help get you pointed in the right direction.

 

--Mark

 


Archive powered by MHonArc 2.6.24.

Top of Page