Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] Multiple meshes with unique testspec's in maddash

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] Multiple meshes with unique testspec's in maddash


Chronological Thread 
  • From: Andrew Lake <>
  • To: Chad Kotil <>
  • Cc:
  • Subject: Re: [perfsonar-user] Multiple meshes with unique testspec's in maddash
  • Date: Wed, 11 Jun 2014 09:49:27 -0400

Hi Chad,

There are no plans to add testspec_id to maddash because the owmesh.conf file
(and thus the spec id) is going away completely in 3.4. You can already
define multiple maddash "checks" that filter on different test parameters
though. For example, for throughput you could have two grids with the exact
same hosts but one is for UDP tests and another is for TCP tests. In the
maddash check definition you'd just need to define a "command" option in one
that has "-p tcp" in one and "-p udp". Likewise you would need to update the
graph URL with whatever extra options it needs to grab the different results
(iirc, bandwidthBraph.cgi has a "protocol=udp/tcp" GET parameter you could
set in this example). I think another way to ask the question is what types
of test parameters do you want to distinguish between tests and are they all
supported as parameters to the graphs and underlying tools?

Thanks,
Andy


On Jun 11, 2014, at 9:22 AM, Chad Kotil
<>
wrote:

> Hello perfsonar-users,
> Is there a way to add multiple meshes to maddash with hosts that are a
> member of multiple testspec's?
>
> I am trying to have maddash display multiple meshes which rely on
> different testspec's as defined in my owmesh.conf. It doesnt look like
> you can specify a testpec_id however in maddash right out of the box.
> The old bwplot.cgi handles this case just fine , as it accepts a
> testspec via the name parameter.
>
> I've done some digging and found that the service check command, the
> graphUrl and metaDataKeyLookup in maddash.yaml do not seem to accept a
> testspec_id. However I was able to modify the service check command,
> check_throughput.pl to accept a testspec and modified the query to match
> on the testspec, so that part does seem to be working. However without
> metaKeyReq.cgi and delayGraph.cgi accepting a testspec_id I think I am
> stuck.
>
> The only thing I can even think to do is use a unique MA, but that is
> not ideal.
>
> Are there any other options available for what I am trying to do? And
> are there any plans to add support for multiple meshes and testspecs
> into maddash?
>
> Thanks,
> --Chad
>




Archive powered by MHonArc 2.6.16.

Top of Page