161 | | === 4.1 Software Installation === |
162 | | Download the latest !OnTimeMeasure release package at http://ontime.oar.net/download/OnTimeMeasure_latest.php. |
163 | | |
164 | | Once you have downloaded the tar file, untar/unzip to see that it contains: |
165 | | |
166 | | * !NodeBeacon.tar.gz |
167 | | * !RootBeacon.tar.gz |
168 | | * README.txt |
169 | | |
170 | | |
171 | | Only the !NodeBeacon.tar.gz is needed. Upload it to a node beacon server and run the following commands to install the measurement service: |
172 | | |
173 | | {{{ |
174 | | tar xzf NodeBeacon.tar.gz |
175 | | cd NodeBeacon/InstallScript |
176 | | chmod +x ontime_software_install.sh |
177 | | ./ontime_software_install.sh |
178 | | }}} |
179 | | |
180 | | === 4.2 Software Configuration === |
181 | | |
182 | | |
183 | | __NTP Configuration__ |
184 | | |
185 | | {{{ |
186 | | sudo vim /etc/ntp.conf |
187 | | }}} |
188 | | Edit the last line to: |
189 | | {{{ |
190 | | server owamp.newy.net.internet2.edu |
191 | | }}} |
192 | | Restart ntpd service |
193 | | {{{ |
194 | | sudo /etc/init.d/ntpd restart |
195 | | }}} |
196 | | |
197 | | __BWCTL Configuration__ |
198 | | |
199 | | Edit the BWCTL config: /etc/bwctld/bwctld.conf |
200 | | |
201 | | Remove the comments on the below lines and edit them as: |
202 | | {{{ |
203 | | allow_unsync |
204 | | sync_fuzz 5 |
205 | | }}} |
206 | | |
207 | | Edit the BWCTL limits: /etc/bwctld/bwctld.limits |
208 | | Change the regular limit to: |
209 | | |
210 | | {{{ |
211 | | limit regular with parent=root, \ |
212 | | duration=30, \ |
213 | | allow_tcp=on, \ |
214 | | allow_udp=on, \ |
215 | | allow_open_mode=on |
216 | | }}} |
217 | | |
218 | | Restart BWCTL: |
219 | | {{{ |
220 | | sudo /etc/init.d/bwctld restart |
221 | | }}} |
222 | | |
223 | | '''Note:''' For more detailed instructions to configure NTP and BWCTL, please refer to the BWCTL Tool website. (http://www.internet2.edu/performance/bwctl/) |
224 | | |
225 | | __Node Beacon invocation options configuration__ |
226 | | |
227 | | {{{ |
228 | | cd NodeBeacon/InstallScript |
229 | | perl config_wizard.pl |
230 | | }}} |
231 | | Follow the steps as directed by the wizard script. |
232 | | |
233 | | __'''''On the Web-portal:'''''__ |
234 | | |
235 | | Login to the [http://ontime.oar.net OnTimeMeasure Researcher Web-portal] and provide the Slice information. |
236 | | |
237 | | |
238 | | === 4.3 Software Invocation === |
239 | | |
240 | | Go to '!NodeBeacon/Datagen/' and run |
241 | | {{{ |
242 | | screen |
243 | | perl file_server.pl |
244 | | }}} |
245 | | If no error is reported, press '<CTRL>+a, c' sequence to open a new blank command window. |
246 | | |
247 | | '''Note:'''Centralize and distributed share the same file server script. If you run both centralized and distributed on the same machine, you only need to run the file_server.pl once. |
248 | | {{{ |
249 | | perl dist_scheduler.pl |
250 | | }}} |
251 | | If no error is reported, press '<CTRL>+a, d' sequence in the SSH window to keep the service running in the background. |
252 | | |
253 | | == 5 Reference == |
254 | | |
255 | | === 5.1 Sample RSpec === |
256 | | |
257 | | An example of a centralized orchestration RSpec that consists of 3 nodes is as follows: |
258 | | |
259 | | {{{ |
260 | | <rspec type="request" xmlns="http://www.protogeni.net/resources/rspec/0.2"> |
261 | | |
262 | | <!-- Fedora Backbone Node --> |
263 | | <!-- Washington Location --> |
264 | | <node component_uuid="urn:publicid:IDN+emulab.net+node+pg41" component_manager_uuid="urn:publicid:IDN+emulab.net+authority+cm" |
265 | | virtual_id="ontime_nodebeacon1" virtualization_type="emulab-vnode" exclusive="1"> |
266 | | <node_type type_name="pc" type_slots="1"/> |
267 | | <interface virtual_id="virt-0"/> |
268 | | </node> |
269 | | |
270 | | <!-- Fedora Backbone Node --> |
271 | | <!-- Kansas Location --> |
272 | | <node component_uuid="urn:publicid:IDN+emulab.net+node+pg43" component_manager_uuid="urn:publicid:IDN+emulab.net+authority+cm" |
273 | | virtual_id="ontime_rootbeacon" virtualization_type="emulab-vnode" exclusive="1"> |
274 | | <node_type type_name="pc" type_slots="1"/> |
275 | | <interface virtual_id="virt-0"/> |
276 | | <interface virtual_id="virt-1"/> |
277 | | </node> |
278 | | |
279 | | <!-- Fedora Backbone Node --> |
280 | | <!-- Utah Location --> |
281 | | <node component_uuid="urn:publicid:IDN+emulab.net+node+pg45" component_manager_uuid="urn:publicid:IDN+emulab.net+authority+cm" |
282 | | virtual_id="ontime_nodebeacon2" virtualization_type="emulab-vnode" exclusive="1"> |
283 | | <node_type type_name="pc" type_slots="1"/> |
284 | | <interface virtual_id="virt-1"/> |
285 | | </node> |
286 | | |
287 | | <!-- Create link between root beacon located in Kansas to node beacon-1 located in Washington --> |
288 | | <link virtual_id="root_beacon_to_node_beacon-1" link_type="ethernet"> |
289 | | <interface_ref virtual_node_id="ontime_rootbeacon" virtual_interface_id="virt-0"/> |
290 | | <interface_ref virtual_node_id="ontime_nodebeacon1" virtual_interface_id="virt-0"/> |
291 | | <bandwidth>1000000</bandwidth> |
292 | | </link> |
293 | | |
294 | | |
295 | | <!-- Create link between root beacon located in Kansas to node beacon-2 located in Utah --> |
296 | | <link virtual_id="root_beacon_to_node_beacon-2" link_type="ethernet"> |
297 | | <interface_ref virtual_node_id="ontime_rootbeacon" virtual_interface_id="virt-1"/> |
298 | | <interface_ref virtual_node_id="ontime_nodebeacon2" virtual_interface_id="virt-1"/> |
299 | | <bandwidth>1000000</bandwidth> |
300 | | </link> |
301 | | |
302 | | </rspec> |
303 | | }}} |
304 | | |
305 | | === 2.3 Sliver Creation and Management === |
306 | | |
307 | | Create and manage a sliver by the Emulab test scripts. |
308 | | |
309 | | - Register a slice |
310 | | {{{ |
311 | | registerslice.py –n <slice name> |
312 | | }}} |
313 | | |
314 | | - Create sliver inside slice |
315 | | {{{ |
316 | | createsliver.py –n <slice name> <rspec file> |
317 | | }}} |
318 | | |
319 | | - Check sliver status |
320 | | {{{ |
321 | | sliverstatus –n <slice name> |
322 | | }}} |
323 | | |
324 | | '''Note:''' You may need to renew your sliver just after successful creation. For this, |
325 | | {{{ |
326 | | renewsliver –n <slice name> <time> |
327 | | }}} |
| 160 | Go to the web portal to add measurement tasks and start the measurement. |