364 | | The first difference is the ability to select which node we want to configure. These tests are always scheduled in a '''star''' configuration, with the node where the tests are being configured as the source endpoint of the test. We will configure the following scheduled tests on our slice: |
365 | | |
366 | | * '''node1:''' |
| 364 | The first difference is the ability to select which node we want to configure. These tests are always scheduled in a '''star''' configuration, originating from the node where the tests are being configured. However, OWAMP (one-way latency) and BWCTL (throughput) tests will run in both directions (managed by the same node). We will configure the following scheduled tests on our slice: |
| 365 | |
| 366 | * '''node1:''' Ping test (default parameters) to node2. One-way delay test (default parameters) to node2. |
| 367 | |
| 368 | * '''node2:''' Throughput test to node1 at 15 minutes interval (all other parameters default). Note that only ''iperf'' is currently installed on the LAMP image. |
| 369 | |
| 370 | Another change from the pS-Performance Toolkit is that we restrict the hosts that can be selected as targets for the tests to the nodes in the slice topology. We use the localname of each node so that the addresses on the virtual topology will be used for the tests (i.e. tests will not go through the control plane). The configuration for each node should look like this: |
| 371 | |
| 372 | [[Image(node1-pinger.png)]] |
| 373 | [[Image(node1-owd.png)]] |
| 374 | [[Image(node2-bwctl.png)]] |
| 375 | |
| 376 | |
| 377 | |