perfSONAR User Q&A and Other Discussion

[Brian Tehan <>]

 

Ivan,

 

I guess I was too impatient on this, the limits file is working on the bottom node.  Thanks for all your help!

 

Brian Tehan

Network Engineer | University of Nebraska ITS

Eppley Administration Building

6001 Dodge St EAB009F, Omaha, NE 68182-0051

402.554.6428 |

 

From: Garnizov, Ivan <>
Sent: Friday, October 29, 2021 1:36 AM
To: Brian Tehan <>;
Subject: RE: Limit throughput tests to specific hours

 

Non-NU Email

---

Hello Brian,

 

I have no idea, what would be the problem on your side for triggering a throughput test with the debug option. Which version of perfSONAR are you running on that host then?

Here is an example of how this works on my side:

 

pscheduler task --debug throughput --source "source-host" --dest "dest-host" --duration PT10S --ip-version 6

 

2021-10-29T06:20:45 Debug started

2021-10-29T06:20:45 Assistance is from localhost

2021-10-29T06:20:45 Forcing default slip of PT5M

2021-10-29T06:20:45 Converting to spec via https://localhost/pscheduler/tests/throughput/spec

Submitting task...

2021-10-29T06:20:46 Fetching participant list

2021-10-29T06:20:46 Spec is: {"source": "source-host", "dest": "dest-host", "duration": "PT10S", "ip-version": 6, "schema": 1}

2021-10-29T06:20:46 Params are: {'spec': '{"source": "source-host", "dest": "dest-host", "duration": "PT10S", "ip-version": 6, "schema": 1}'}

2021-10-29T06:20:47 Got participants: {'participants': ['source-host', 'dest-host']}

2021-10-29T06:20:47 Lead is source-host

2021-10-29T06:20:47 Pinging https://source-host/pscheduler/

2021-10-29T06:20:47 source-host is up

2021-10-29T06:20:47 Posting task to https://source-host/pscheduler/tasks

2021-10-29T06:20:47 Data is {'schedule': {'slip': 'PT5M'}, 'test': {'spec': {'source': 'source-host', 'dest': 'dest-host', 'duration': 'PT10S', 'ip-version': 6, 'schema': 1}, 'type': 'throughput'}}

Task URL:

https://source-host/pscheduler/tasks/216d1223-54a4-4a74-83ee-788b12d37365

2021-10-29T06:21:16 Posted https://source-host/pscheduler/tasks/216d1223-54a4-4a74-83ee-788b12d37365

2021-10-29T06:21:17 Submission diagnostics:

2021-10-29T06:21:17   Hints:

2021-10-29T06:21:17     requester: requesterIP

2021-10-29T06:21:17     server: ServerIP

2021-10-29T06:21:17   Identified as everybody

2021-10-29T06:21:17   Classified as default

2021-10-29T06:21:17   Application: Defaults applied to non-friendly hosts

2021-10-29T06:21:17     Group 1: Limit 'innocuous-tests' failed: Passed but inverted

2021-10-29T06:21:17     Group 1: Limit 'throughput-default-time' passed

2021-10-29T06:21:17     Group 1: Limit 'throughput-default-udp' failed: UDP testing not allowed

2021-10-29T06:21:17     Group 1: Limit 'idleex-default' failed: Test is not 'idleex'

2021-10-29T06:21:17     Group 1: Want any, 1/4 passed, 3/4 failed: PASS

2021-10-29T06:21:17     Application PASSES

2021-10-29T06:21:17   Proposal meets limits

2021-10-29T06:21:17   Priority set to default of 0

Running with tool 'iperf3'

Fetching first run...

2021-10-29T06:21:17 Fetching https://source-host/pscheduler/tasks/216d1223-54a4-4a74-83ee-788b12d37365/runs/first

2021-10-29T06:21:26 Handing off: pscheduler watch --first --debug https://source-host/pscheduler/tasks/216d1223-54a4-4a74-83ee-788b12d37365

2021-10-29T06:21:27 Debug started

2021-10-29T06:21:27 Fetching https://source-host/pscheduler/tasks/216d1223-54a4-4a74-83ee-788b12d37365

2021-10-29T06:21:28 Fetching next run from https://source-host/pscheduler/tasks/216d1223-54a4-4a74-83ee-788b12d37365/runs/first

 

Next scheduled run:

https://source-host/pscheduler/tasks/216d1223-54a4-4a74-83ee-788b12d37365/runs/cee71e48-1ee5-476a-b1e2-4752695856d6

Starts 2021-10-29T06:21:26Z (~0 seconds)

Ends   2021-10-29T06:21:45Z (~15 seconds)

Waiting for result...

 

In bold is the section you are interested in. If your version of pS does not allow running the command as per the given examples, please update to the latest.

Still in the meantime you can also check the pscheduler logs in: /var/log/pscheduler/pscheduler.log, where you should be able to find the same output, but mixed with logs from other events.

 

 

Regards,

Ivan Garnizov

 

GEANT WP6T3: pS development team

GEANT WP7T1: pS deployments GN Operations

GEANT WP9T2: Software governance in GEANT

 

 

 

 

From: Brian Tehan []
Sent: Thursday, October 28, 2021 4:36 PM
To: Garnizov, Ivan (RRZE) <>;
Subject: RE: Limit throughput tests to specific hours

 

$ sudo pscheduler debug on

$ sudo pscheduler task throughput --bandwidth 1M --dest 162.127.1.1

Submitting task...

Task URL:

https://localhost/pscheduler/tasks/b72fb685-f2b8-4a9e-b8cb-d33c8a8b83d2

Running with tool 'iperf3'

Fetching first run...

 

Next scheduled run:

https://localhost/pscheduler/tasks/b72fb685-f2b8-4a9e-b8cb-d33c8a8b83d2/runs/336d7b93-f7fd-4275-a5d8-151e8380275f

Starts 2021-10-28T09:29:02-05 (~6 seconds)

Ends   2021-10-28T09:29:21-05 (~18 seconds)

Waiting for result...

 

* Stream ID 5

Interval       Throughput     Retransmits    Current Window

0.0 - 1.0      1.72 Mbps      0              127.42 KBytes 

1.0 - 2.0      1.05 Mbps      0              131.77 KBytes 

2.0 - 3.0      1.05 Mbps      0              134.66 KBytes 

3.0 - 4.0      1.05 Mbps      0              144.80 KBytes 

4.0 - 5.0      1.05 Mbps      0              144.80 KBytes 

5.0 - 6.0      1.05 Mbps      0              133.22 KBytes 

6.0 - 7.0      1.05 Mbps      0              139.01 KBytes 

7.0 - 8.0      0.00bps        0              139.01 KBytes 

8.0 - 9.0      1.05 Mbps      0              144.80 KBytes 

9.0 - 10.0     1.05 Mbps      0              133.22 KBytes 

 

Summary

Interval       Throughput     Retransmits    Receiver Throughput

0.0 - 10.0     1.01 Mbps      0              1.01 Mbps

 

No further runs scheduled.

$

 

 

 

 

Ivan,

 

I wasn’t able to get a -debug flag to work on the pscheduler task command, the only thing I could find was to do the above pscheduler debug on command.  Otherwise the throughput test went through fine with the default limits file.

 

Thanks.

 

Brian Tehan

Network Engineer | University of Nebraska ITS

Eppley Administration Building

6001 Dodge St EAB009F, Omaha, NE 68182-0051

402.554.6428 |

 

From: Garnizov, Ivan <>
Sent: Thursday, October 28, 2021 8:59 AM
To: Brian Tehan <>;
Subject: RE: Limit throughput tests to specific hours

 

Non-NU Email

---

Hello Brian,

That seems quite strange, but there are more steps to consider…

Now it is time to initiate a throughput test on the CLI with the –debug option.

 

Please provide the output of this command with the missing parameters added

 

pscheduler task –debug throughput –source … --dest

 

 

Regards,

Ivan Garnizov

 

GEANT WP6T3: pS development team

GEANT WP7T1: pS deployments GN Operations

GEANT WP9T2: Software governance in GEANT

 

 

 

From: Brian Tehan []
Sent: Thursday, October 28, 2021 3:29 PM
To: Garnizov, Ivan (RRZE) <>;
Subject: RE: Limit throughput tests to specific hours

 

Ivan,

 

Thanks for reminding me about the validate-limits command, I saw the same errors as you did.  I fixed those by changing the classifier like you suggested, in this case to default.  I had the attached limits file as the operational file last night, but bandwidth tests still took place outside of the specified time range.  I’ve changed my backup of the original file to the operational one and renamed mine to testing.  Any other ideas on how I can get throughput testing to be limited to a specific time frame?

 

Thanks!

 

Brian Tehan

Network Engineer | University of Nebraska ITS

Eppley Administration Building

6001 Dodge St EAB009F, Omaha, NE 68182-0051

402.554.6428 |

 

From: Garnizov, Ivan <>
Sent: Wednesday, October 27, 2021 10:30 AM
To: Brian Tehan <>;
Subject: RE: Limit throughput tests to specific hours

 

Non-NU Email

---

Hello Brian,

 

There are problems with your limits file.

You should always check the draft limits file before replacing the operational one.

 

So here is the result:

@r72 ~]$ pscheduler validate-limits limits-brian.conf

Unknown classifiers: allowed-tests, throughput-only-at-night

@r72 ~]$

 

 

It appears the syntax of your limits file is correct. But you haven’t declared 2 groups of clients, which are stated in your Applications statements.

In my example I have generalized on use of Classifiers… in your example I see:

 

    "classifiers": [

                {

                    "name": "default",

                    "description": "Everybody",

                    "identifiers": [ "everybody" ]

                },

                {

                    "name": "friendlies",

                    "description": "Identifiers we find friendly",

                    "identifiers": [ "local-interfaces" ]

                },

                {

                    "name": "hostiles",

                    "description": "Identifiers we find unfriendly",

                    "identifiers": [ "hackers", "bogons" ]

                }

    ],

 

 

Meaning you should either use one of those or add specific declarations for the “allowed-tests”, “throughput-only-at-night”

 

 

Regards,

Ivan Garnizov

 

GEANT WP6T3: pS development team

GEANT WP7T1: pS deployments GN Operations

GEANT WP9T2: Software governance in GEANT

 

 

 

From: Brian Tehan []
Sent: Wednesday, October 27, 2021 4:48 PM
To: Garnizov, Ivan (RRZE) <>
Subject: RE: Limit throughput tests to specific hours

 

Hey Ivan,

 

I feel like I’m on the cusp of understanding the limits file, thank you for your help!  I’ve attached my limits.conf file where I’ve added 3 items to the bottom of the LIMITS section, and 2 items to the bottom of the APPLICATIONS section.  Would you mind taking a look and letting me know if you see any problems?

 

Thanks.

 

Brian Tehan

Network Engineer | University of Nebraska ITS

Eppley Administration Building

6001 Dodge St EAB009F, Omaha, NE 68182-0051

402.554.6428 |

 

From: Garnizov, Ivan <>
Sent: Wednesday, October 27, 2021 2:03 AM
To: Brian Tehan <>
Subject: RE: Limit throughput tests to specific hours

 

Non-NU Email

---

Hello Brian,

 

As discussed earlier the pScheduler Limit for the “run-schedule” will control or restrict in which times tests can be scheduled.

Now if you would like to specify the type of the test, I would suggest doing that through the directive: test-type http://docs.perfsonar.net/config_pscheduler_limits.html#test-type-check-test-type

Then you combine both Limit directives in an Application in order to achieve the combination of both restrictions.

Say for example if the names of your Limit directives are (please note the name field are identifiers):

• “throughput-allowed-slot”
• “throughput-test-type”

Then your pScheduler Limit application should state:

 

{

            "description": "Allow Throughput tests in a certain period of time.... etc",

            "classifier": "allowed-parties-for-throughput",

            "apply": [

                {

                    "require": "all",

                    "limits": [ "throughput-allowed-slot", “throughput-test-type” ]

                }

            ]

        },

 

 

Regards,

Ivan Garnizov

 

GEANT WP6T3: pS development team

GEANT WP7T1: pS deployments GN Operations

GEANT WP9T2: Software governance in GEANT

 

 

 

From: Brian Tehan []
Sent: Tuesday, October 26, 2021 8:44 PM
To: Garnizov, Ivan (RRZE) <>
Subject: RE: Limit throughput tests to specific hours

 

Thanks for the breakdown, Ivan.  Is there any way to limit just throughput tests to specific hours though?

 

Thanks!

 

Brian Tehan

Network Engineer | University of Nebraska ITS

Eppley Administration Building

6001 Dodge St EAB009F, Omaha, NE 68182-0051

402.554.6428 |

 

From: Garnizov, Ivan <>
Sent: Tuesday, October 26, 2021 6:28 AM
To: Brian Tehan <>
Subject: RE: Limit throughput tests to specific hours

 

Non-NU Email

---

Hello Brian,

 

The pScheduler Limits directive you refer to is a limiter / blocker for a group of remote systems to prevent them, even deny, execution of the specified tests in the limit directive.

The group of systems would be identified by the Identifier and the Classifier you have assigned with this Limit in an Application.

 

This will lead to runs falling outside the specified criteria being rejected…in other words will turn as “Non-Starters”.

 

Please note that at first the “Non-Starters” will appear as the “conflict” appears. After 24h the Non-Starters will appear as they are being scheduled.

 

Regards,

Ivan Garnizov

 

GEANT WP6T3: pS development team

GEANT WP7T1: pS deployments GN Operations

GEANT WP9T2: Software governance in GEANT

 

 

 

From: [] On Behalf Of Brian Tehan
Sent: Monday, October 25, 2021 11:54 PM
To:
Subject: [perfsonar-user] Limit throughput tests to specific hours

 

https://docs.perfsonar.net/config_pscheduler_limits.html#run-schedule-check-attributes-of-the-run-time

 

Hello,

 

I’m using PWA to build latency and throughput tests and they’re showing up in MaDDash, however I’d like to limit the throughput tests to specific hours.  Would I be able to use run-schedule in the limits.conf file to accomplish this?  Or would there be a better way to go about this?

 

Thanks.

 

Brian Tehan

Network Engineer | University of Nebraska ITS

Eppley Administration Building

6001 Dodge St EAB009F, Omaha, NE 68182-0051

402.554.6428 |