Allow extra user plugins in pbs_benchpress

Forum discussion: http://community.pbspro.org/t/allow-extra-user-plugins-in-pbs-benchpress/1254

PR: https://github.com/PBSPro/pbspro/pull/853

Currently pbs_benchpress in PTL has hard coded list of plugins which gets loaded from ptl.utils.plugins directory. Due to hard coded list, it doesn’t allow user to load custom plugin to do extra stuff before and after test runs. For example force restart server before each test case or send test execution status to some central database etc…

So this change will allow user to write PTL plugin which can be loaded by pbs_benchpress.

Interface: New option '--user-plugins' to pbs_benchpress

• Visibility: public
• Change Control: Stable
• Synopsis: A new option '--user-plugins' to pbs_benchpress to specify PTL plugins
• Details: This new option allows user to specified comma separated key value pair of PTL plugins which will loaded at run time in pbs_benchpress. From key value pair, key should be module name (for example 'myplugins.xyzplugin') and value should be plugin class name (for example 'XYZPlugin') and plugin class should be subclass of 'nose.plugins.base.Plugin' and all custom plugins' module should be included in PYTHONPATH environment variable or it should be placed in default installation directory for python modules (i.e. site-packages directory). If pbs_benchpress fails to load plugin module or fails to find plugin class in module or if plugin class is not subclass of 'nose.plugins.base.Plugin' then it will exit immediately with proper error message. 

OSS Site Map

Project Documentation Main Page

Developer Guide Pages