Changes between Version 1 and Version 2 of OTM-CRONInstall

Timestamp:

11/01/10 18:57:44 (13 years ago)

Author:

zhu.249@osu.edu

Comment:

--

OTM-CRONInstall

@@ -157 +157 @@
 If no error is reported, press '<CTRL>+a, d' sequence in the SSH window to keep the service running in the background.
 
-== 4. Distributed Case Installation ==
 
-=== 4.1 Software Installation ===
-Download the latest !OnTimeMeasure release package at http://ontime.oar.net/download/OnTimeMeasure_latest.php.
-
-Once you have downloaded the tar file, untar/unzip to see that it contains:
-
- * !NodeBeacon.tar.gz
- * !RootBeacon.tar.gz
- * README.txt
-
-
-Only the !NodeBeacon.tar.gz is needed. Upload it to a node beacon server and run the following commands to install the measurement service:
-
-{{{
-tar xzf NodeBeacon.tar.gz
-cd NodeBeacon/InstallScript
-chmod +x ontime_software_install.sh
-./ontime_software_install.sh
-}}}
-
-=== 4.2 Software Configuration ===
-
-
-__NTP Configuration__
-
-{{{
-sudo vim /etc/ntp.conf
-}}}
-Edit the last line to: 
-{{{
-server owamp.newy.net.internet2.edu
-}}}
-Restart ntpd service
-{{{
-sudo /etc/init.d/ntpd restart
-}}}
-
-__BWCTL Configuration__
-
-Edit the BWCTL config: /etc/bwctld/bwctld.conf
-
-Remove the comments on the below lines and edit them as:
-{{{
-allow_unsync
-sync_fuzz 5
-}}}
-
-Edit the BWCTL limits: /etc/bwctld/bwctld.limits
-Change the regular limit to:
-
-{{{
-limit regular with parent=root, \
-        duration=30, \
-        allow_tcp=on, \
-        allow_udp=on, \
-        allow_open_mode=on
-}}}
-
-Restart BWCTL:
-{{{
-sudo /etc/init.d/bwctld restart
-}}}
-
-'''Note:''' For more detailed instructions to configure NTP and BWCTL, please refer to the BWCTL Tool website. (http://www.internet2.edu/performance/bwctl/)
-
-__Node Beacon invocation options configuration__
-
-{{{
-cd NodeBeacon/InstallScript
-perl config_wizard.pl
-}}}
-Follow the steps as directed by the wizard script.
-
-__'''''On the Web-portal:'''''__
-
-Login to the [http://ontime.oar.net OnTimeMeasure Researcher Web-portal] and provide the Slice information.
-
-
-=== 4.3 Software Invocation ===
-
-Go to '!NodeBeacon/Datagen/' and run
-{{{
-screen
-perl file_server.pl
-}}}
-If no error is reported, press '<CTRL>+a, c' sequence to open a new blank command window.
-
-'''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.
-{{{
-perl dist_scheduler.pl
-}}}
-If no error is reported, press '<CTRL>+a, d' sequence in the SSH window to keep the service running in the background.
-
-== 5 Reference ==
-
-=== 5.1 Sample RSpec ===
-
-An example of a centralized orchestration RSpec that consists of 3 nodes is as follows:
-
-{{{
-<rspec type="request" xmlns="http://www.protogeni.net/resources/rspec/0.2">
-
-<!-- Fedora Backbone Node -->
-<!-- Washington Location -->
-<node component_uuid="urn:publicid:IDN+emulab.net+node+pg41" component_manager_uuid="urn:publicid:IDN+emulab.net+authority+cm" 
-virtual_id="ontime_nodebeacon1" virtualization_type="emulab-vnode" exclusive="1">
-    <node_type type_name="pc" type_slots="1"/>
-    <interface virtual_id="virt-0"/>
-</node>
-
-<!-- Fedora Backbone Node -->
-<!-- Kansas Location -->
-<node component_uuid="urn:publicid:IDN+emulab.net+node+pg43" component_manager_uuid="urn:publicid:IDN+emulab.net+authority+cm" 
-virtual_id="ontime_rootbeacon" virtualization_type="emulab-vnode" exclusive="1">
-    <node_type type_name="pc" type_slots="1"/>
-    <interface virtual_id="virt-0"/>
-    <interface virtual_id="virt-1"/>
-</node>
-
-<!-- Fedora Backbone Node -->
-<!-- Utah Location -->
-<node component_uuid="urn:publicid:IDN+emulab.net+node+pg45" component_manager_uuid="urn:publicid:IDN+emulab.net+authority+cm" 
-virtual_id="ontime_nodebeacon2" virtualization_type="emulab-vnode" exclusive="1">
-        <node_type type_name="pc" type_slots="1"/>
-        <interface virtual_id="virt-1"/>
-</node>
-
-<!-- Create link between root beacon located in Kansas to node beacon-1 located in  Washington -->
- <link virtual_id="root_beacon_to_node_beacon-1" link_type="ethernet">
-    <interface_ref virtual_node_id="ontime_rootbeacon" virtual_interface_id="virt-0"/>
-    <interface_ref virtual_node_id="ontime_nodebeacon1" virtual_interface_id="virt-0"/>
-    <bandwidth>1000000</bandwidth>
-  </link>
-
-
-<!-- Create link between root beacon located in Kansas to node beacon-2 located in Utah -->
- <link virtual_id="root_beacon_to_node_beacon-2" link_type="ethernet">
-    <interface_ref virtual_node_id="ontime_rootbeacon" virtual_interface_id="virt-1"/>
-    <interface_ref virtual_node_id="ontime_nodebeacon2" virtual_interface_id="virt-1"/>
-    <bandwidth>1000000</bandwidth>
-  </link>
-
-</rspec>
-}}}
-
-=== 2.3 Sliver Creation and Management ===
-
-Create and manage a sliver by the Emulab test scripts.
-
--       Register a slice
-{{{
-registerslice.py –n <slice name>
-}}}
-
--       Create sliver inside slice
-{{{
-createsliver.py –n <slice name> <rspec file>
-}}}
-
--       Check sliver status
-{{{
-sliverstatus –n <slice name>
-}}}
-
-'''Note:''' You may need to renew your sliver just after successful creation. For this,
-{{{
-renewsliver –n <slice name> <time>
-}}}
+Go to the web portal to add measurement tasks and start the measurement.