Changes between Version 8 and Version 9 of GENIFIRE/Labwiki/Part0/DesignSetup
- Timestamp:
- 07/07/14 17:20:28 (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GENIFIRE/Labwiki/Part0/DesignSetup
v8 v9 5 5 In this example, we will use the [https://mytestbed.net/projects/omlapp/repository/iperf/entry/oml/iperf.rb.in?rev=oml%2Fmaster Iperf Application] and [https://github.com/mytestbed/oml4r/blob/master/omf/ping-oml2.app.rb Ping Application] 6 6 7 However, for your own topology , choose an application that best suits your purpose.7 However, for your own topology outside this tutorial, choose an application that best suits your purpose. 8 8 9 9 A list of available applications is given here: … … 12 12 == 2. Write OEDL Application == 13 13 14 For this tutorial, Sec 2.1 - Sec 2.3 are for understanding the OEDL script that '''we have preloaded into !LabWiki for you'''. When you write your own applications it is advised to open and editor of your choice and define your experiment scripts similar to the procedure described here. 15 14 16 === 2.1 Define Property === 17 18 An experiment property maybe described as any variable entity you wish to define for your experiment. Generally this would be the name of your resources (hostname-slicename) that you will use but it can also include IP addresses, Port numbers and so on. Properties defined within quotes are treated as strings. 15 19 16 20 {{{ … … 25 29 defProperty('sinkaddr12', '10.0.5.101', "Ping destination address") 26 30 27 28 31 }}} 29 32 … … 33 36 The entire application definition for OML-Iperf is given [http://mytestbed.net/projects/omlapp/repository/iperf/entry/oml/iperf.rb.in?rev=oml%2Fmaster here] 34 37 35 Select the definition you will use in your experiment. The Application definition includes the properties and measurement parameters 38 Select the definition you will use in your experiment. The Application definition includes the experiment properties and measurement parameters. 39 For an Iperf, the properties would be similar to what you run on the command line, i.e, select whether server or client, TCP or UDP and so on. The measurement parameters would be throughput, packet loss, jitter and so on. 36 40 37 41 … … 70 74 === 2.3 Define Group and add Applications=== 71 75 76 A Group is a set of resources on which you want to run your experiment. Here, we see a group definition with just one resource but we can run the same set of applications on a set of resources. 77 For example, change defGroup('theReceiver', property.thelistener) to defGroup('theReceiver', property.thelistener1, property.listener2) if you have more than one resource on which you want to run an Iperf server. 72 78 a) Server Group [[BR]] 73 79 … … 110 116 === 2.3 Define Experiment Event === 111 117 118 The experiment event will include the exact order of applications you wish to run. 119 112 120 ==== 2.3.1 Traffic Control ==== 113 121 The Traffic control code limits traffic from server to client, so that you will see throughput reducing as time passes. 114 122 115 123 {{{ … … 130 138 ==== 2.3.2 Define Events ==== 131 139 140 Some events are time-based. For examble, you want to start the Iperf server before the client starts. To ensure this, you can select the Iperf server group to run applications as soon as the resources are configured. We can wait for about 3 seconds before we run the client. Below, we start one Iperf stream from client to server. After 10 seconds, we start a second stream from client to server. 132 141 133 142 {{{
