Changes between Version 1 and Version 2 of Tutorials/c0WiFi/Tutorial4
- Timestamp:
- Oct 15, 2014, 4:33:24 PM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Tutorials/c0WiFi/Tutorial4
v1 v2 233 233 In the above measurement point definition, ''packets'' is a measurement point that's already defined in the iperf application. Next the metrics are defined with a name (already defined in the iperf app) along with it's object type. 234 234 235 * Since each client starts an iperf session at staggered time intervals, we define multiple client groups with only one node associated in each group. 235 * Since each client starts an iperf session at staggered time intervals, we define multiple client groups with only one node associated in each group. This will allow us to start iperf on a per group basis. 236 236 {{{ 237 237 res = property.client.value.split(',') … … 255 255 end 256 256 }}} 257 257 Note that the original group definition has been wrapped around with some Ruby code: 258 1. Each ''defGroup'' is given a unique identifier (ie. client'''1''', client'''2''', etc...) 259 2. The ''ip address'' is assigned with a Ruby variable. 260 261 A few more parameters are passed to the iperf application to enable recording all the defined measurement points: 262 1. The ''oml-server'' is set to oml:3003. This is send all the measurements to the OML server running on the console. 263 2. The ''oml-id'' and ''oml-exp-id'' is associated with the ID of the experiment so the ''results service'' can fetch the recorded data. 264 3. The ''reportstyle'' is set for OML recording. 265