Changes between Version 2 and Version 3 of GEMINI/Tutorial/GEC14


Ignore:
Timestamp:
07/15/13 10:59:02 (11 years ago)
Author:
carpenter@vis.uky.edu
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GEMINI/Tutorial/GEC14

    v2 v3  
    582582GEMINI also provides a way to schedule regular throughput measurements. Scheduling this type of test is very similar to scheduling One-Way Delay and Ping tests. We schedule active tests by accessing the pSConfig web UI (see [#a8.1AccessingpSConfigUI 8.1 Accessing pSConfig UI]). ''NOTE: We recommend doing a Pull Configuration before starting this section to avoid race conditions.''
    583583
    584 Access the Schedule Tests page, select the node that will perform the measurements (PCA) and then click the Add New Throughput Test button. ''NOTE: We have already enabled the necessary service for regular throughput testing when doing section [http://groups.geni.net/geni/wiki/GEMINITutorial#a8.2EnablingServices 8.2 Enabling Services].''
     584Access the Schedule Tests page, select the node that will perform the measurements (PCA) and then click the Add New Throughput Test button. ''NOTE: We have already enabled the necessary service for regular throughput testing when doing section [#a8.2EnablingServices 8.2 Enabling Services].''
    585585
    586586[[Image(psconfig-schedbwctl.png)]]
    … …  
    604604[[Image(psconfig-schedbwctl-push.png)]]
    605605
    606 To speed up the propagation of changes, you can perform the steps in [http://groups.geni.net/geni/wiki/GEMINITutorial#a8.4ApplyingtheConfiguration 8.4 Applying the Configuration]. We've only changed the tests configured for node PCA, so there is no need to apply the configuration on other nodes.
     606To speed up the propagation of changes, you can perform the steps in [#a8.4ApplyingtheConfiguration 8.4 Applying the Configuration]. We've only changed the tests configured for node PCA, so there is no need to apply the configuration on other nodes.
    607607
    608608==== 12.2.1 Visualizing Regular Throughput Measurements ====
    609609
    610 To visualize our scheduled throughput tests we follow similar steps to section [http://groups.geni.net/geni/wiki/GEMINITutorial#a10.1AccessingperfAdminforActiveMeasurementsData 10.1 Accessing perfAdmin for Active Measurements Data]. When accessing perfAdmin, the list of services shown will be the data we got from our last pull. The perfSONAR BUOY BWCTL service wasn't there because we didn't have any throughput tests scheduled back then. Now that we do, we need to do a Pull of data from UNIS to update the list. ''NOTE: It may take a while for the service to show (the time it takes to get data from the test and for the service to notice the new data). ''
     610To visualize our scheduled throughput tests we follow similar steps to section [#a10.1AccessingperfAdminforActiveMeasurementsData 10.1 Accessing perfAdmin for Active Measurements Data]. When accessing perfAdmin, the list of services shown will be the data we got from our last pull. The perfSONAR BUOY BWCTL service wasn't there because we didn't have any throughput tests scheduled back then. Now that we do, we need to do a Pull of data from UNIS to update the list. ''NOTE: It may take a while for the service to show (the time it takes to get data from the test and for the service to notice the new data). ''
    611611
    612612[[Image(perfadmin-bwctl-pull.png)]]