perfsonar-user - Re: [perfsonar-user] [non-nasa source] [EXTERNAL] FW: Defining single-ended throughput tests inside a psconfig template
Subject: perfSONAR User Q&A and Other Discussion
List archive
Re: [perfsonar-user] [non-nasa source] [EXTERNAL] FW: Defining single-ended throughput tests inside a psconfig template
Chronological Thread
- From: "Uhl, George D. (GSFC-423.0)[SGT INC]" <>
- To: "" <>
- Subject: Re: [perfsonar-user] [non-nasa source] [EXTERNAL] FW: Defining single-ended throughput tests inside a psconfig template
- Date: Wed, 14 Aug 2019 13:51:29 +0000
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=nasa.gov; dmarc=pass action=none header.from=nasa.gov; dkim=pass header.d=nasa.gov; 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-SenderADCheck; bh=zBEysUQy/cF1nFTKZ24CngA5RmAd/FI6l8QPLvJhWaY=; b=YjvXCVFxGVYBCQjpXBoTopd4wpRqTvO51+23mLJTNMAlud9gmapG6CrEbI2+TPqKAnI59+Bdm+prZN573mo7w8O3X4VmAzK7Th52pqqr7rTK/JWkhhcAhzt8aDU7t0lTk43opD7Z8Jz0NAbLNTLSPpBtrwTi8T5B8L5KQbOyY4+x11CE79US7MOUefQ3LSSDRRvA5eNfqmNr18Nld2n13weGI/hEXrWstn6mI5gtGO6obF22WQtacxpJdZqL+PKHK/boRI1ibgsp8V6D0JqbhPdnSEdfDxlR+HAnlS2sB04+MybNh9ejBiI/9KCyI1kH6aePD0W5wWQPh+RkDWGquw==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=PrdXLrL1Jqidyg9rq9di1D8e6BMMObXBqXYPu8ubo1XZzrgHJE/Z7rhgxcWh39lT9I9sHEWJTLj3ABT/Ay4smfgInzO72+2JPX2lFCOVmEcEqQCDfpnLMLuM89IU/J/jLdVIw/p59EvQB0aE78LkjYuf15cXW/JRVMIQW48v59oOCqy0VSvXdnppR2dKwQ0VOoIOLBOKpyBNxvFhbh4SonCVlQfqisMJk56Ffk5zuRFEYm+D+OYi8g78RaHk/2xDkMzE4/Ggos17/dijImClUROkCxV6tBV+4LYU75SoHcKza7Vrm/bpckGUbopvVxkzvr0DXzXkJsSBD4qlQgAzYg==
- Dkim-filter: OpenDKIM Filter v2.11.0 ndjsvnpf103.ndc.nasa.gov 3D8454007BCB
Hi,
I’m remembering what Mark Feit said a few months ago:
The JSON that goes into a pSConfig test template is the same JSON that the test spec that “pscheduler task --export throughput …” would produce. Any parameter available for that test (or any other) is available for pSConfig, too. The throughput test has a “reverse” option (see “pscheduler task throughput --help”) that can be put into a template:
{ "dest": "{% address[1] %}", "reverse": true }
This answers the question about defining single-ended tests in a psconfig template. However will the results of a single-ended test be extractable from Esmond via a maddash dashboard or would I need to use a different Nagios check than the “check_throughput.pl”? As I recall, the reverse option in a psconfig defined throughput test did not produce reverse direction throughput results from “check_throughput.pl” because the source and destination test nodes as defined in the test remain unchanged in the reverse test.
Thanks, George
From: <> on behalf of <Uhl>, "George D. [SGT INC] (GSFC-423.0)" <>
Forwarding to perfsonar-user list.
From: "George.D.Uhl" <>
Hi,
I have a non-perfsonar test host that I am able run a single-ended throughput test with from one of my managed hosts by using pscheduler on the CLI. I am able to test in the reverse direction using the –reverse option although at the cost of getting non-reported retransmits and current window values. From the documentation I can’t determine if single-ended throughput testing is supported other than using the CLI. Is it possible to include single-ended tests in a psconfig template? If so, could the test results be stored in a measurement archive such that the throughput rates are stored in both the forward and reverse directions? Would I be able to extract this data using a maddash dashboard?
Thanks, George |
- Re: [perfsonar-user] [non-nasa source] [EXTERNAL] FW: Defining single-ended throughput tests inside a psconfig template, Uhl, George D. (GSFC-423.0)[SGT INC], 08/14/2019
Archive powered by MHonArc 2.6.19.