Changes between Version 2 and Version 3 of GEMINI/Tutorial/GEC19/GENI_Desktop_and_GEMINI_blipp/ExecuteExperiment


Ignore:
Timestamp:
03/10/14 02:38:49 (6 years ago)
Author:
mkeele@indiana.edu
Comment:

updates for blipp log

Legend:

Unmodified
Added
Removed
Modified
  • GEMINI/Tutorial/GEC19/GENI_Desktop_and_GEMINI_blipp/ExecuteExperiment

    v2 v3  
    3232----
    3333
     34From the 'Schedule BLiPP Test' page click 'BLiPP Log' to see that a BLiPP instance is running.
     35
     36----
     37[[Image(wiki:GEMINI/Tutorial/Images:start_blipp_log.png)]]
     38----
     39
    3440Select a node to configure from the dropdown menu [[Image(wiki:GEMINI/Tutorial/Images:select_node.png)]], then select an active test to configure.
    3541
     
    3945----
    4046
    41 Once configured, BLiPP will poll UNIS, update its configuration, and begin collecting the desired measurements.  The event types for each measurement will be displayed alongside each scheduled test row.  Once data is available (give it a few minutes to begin collecting!), you can select an event type and display the associated graph.
     47Once configured, BLiPP will poll UNIS, update its configuration, and begin collecting the desired measurements.  The scheduled measurement will be seen below in the log. The event types for each measurement will be displayed alongside each scheduled test row.  Once data is available (give it a few minutes to begin collecting!), you can select an event type and display the associated graph.
     48
     49----
     50[[Image(wiki:GEMINI/Tutorial/Images:ping_blipp_log.png)]]
     51----
    4252
    4353NOTE: For throughput testing, no assumption is made about listening servers.  For example, an iperf test will attempt to connect to the specified host at each interval, but if no iperf server is listening, no result will be collected.  Future work will allow BLiPP to start a throughput listener on another node within the slice.