Original issue 874 created by arlake228 on 2014-03-31T15:36:05.000Z:
Folks have requested the ability to define their own custom probes that can be executed by bwctld. I'm not sure of is what the semantics of this would be. The way bwctl normally works, you have a 'sender' bwctld and a 'catcher' bwctld. The client connects to each and requests the test to be performed, and the catcher spawns a server instance, and the sender spawns a client instance. In the 'custom probe' route, the 'sender' and 'catcher' concepts probably go away because a client can't be sure that each bwctld instance has the same custom probe(s) configured. Another open question is how bwctld's probes get specified/used. I'd presume that most folks would want to be able to define multiple probes, and at that point, how do the probes get specified and/or advertised? Since bwctl supports third-party tests, who gets to spawn these custom probes? How do they pass parameters to the probe? I'd presume there are some security questions with passing the parameters as a string, but there are probably ways we could parse the string in bwctld to avoid the security issues.
arlake228
commented
9 years ago
From @arlake228 on March 14, 2015 12:10
Original issue 874 created by arlake228 on 2014-03-31T15:36:05.000Z:
Folks have requested the ability to define their own custom probes that can be executed by bwctld. I'm not sure of is what the semantics of this would be. The way bwctl normally works, you have a 'sender' bwctld and a 'catcher' bwctld. The client connects to each and requests the test to be performed, and the catcher spawns a server instance, and the sender spawns a client instance. In the 'custom probe' route, the 'sender' and 'catcher' concepts probably go away because a client can't be sure that each bwctld instance has the same custom probe(s) configured. Another open question is how bwctld's probes get specified/used. I'd presume that most folks would want to be able to define multiple probes, and at that point, how do the probes get specified and/or advertised? Since bwctl supports third-party tests, who gets to spawn these custom probes? How do they pass parameters to the probe? I'd presume there are some security questions with passing the parameters as a string, but there are probably ways we could parse the string in bwctld to avoid the security issues.
Copied from original issue: perfsonar/project#872