Version 1 (modified by 13 years ago) (diff) | ,
---|
OnTimeMeasure-GENI Installation Document
Prasad Calyam, Kunpeng Zhu
Nov 01, 2010
Software License: 'GENI Project License (GPL)'
1. Getting Started
This document describes the installation, configuration and usage of OnTimeMeasure, which is a prototype measurement service for the GENI facility users. The measurement service can be used to perform centralized and distributed orchestration and provisioning of active measurements within experiment slices for purposes such as:
- Network paths monitoring
- Network weather forecasting
- Network performance anomaly detection
- Network-bottleneck fault-location diagnosis
The 'OnTimeMeasure researcher web-portal' enables ProtoGENI/Emulab and PlanetLab users to register, create and monitor experiment slices on geographically distributed resources in their facility.
Before proceeding further, we highly recommend reading the Early Experimenter Tutorial.
2. Requirements
The OnTimeMeasure software package has the following requirements:
- Operating System: Ubuntu 10.04 x64
- Open Ports: For RootBeacon server: MySQL TCP/3306, Graphite TCP/2003 and TCP/17280, Collector TCP/7777, HTTP TCP/17290; For NodeBeacon server: BWCTL TCP/4823, Nodescheduler TCP/17249, HTTP TCP/17290
- User Accounts: User must have registered accounts in the OnTimeMeasure Researcher Web-portal and CRON Testbed
- CRON slice: Create a new experimental slice in CRON with at least 3 nodes. One acts an extra role of the root beacon.
Note: Following are the pre-requisite software and Perl modules, which will be installed automatically by the scripts delivered in the OnTimeMeasure release package.
Pre-requisite Software: MySQL, Graphite, Perl, Python, Iperf, Ruby, Bwctl-server, Bwctl-client, Cairo, Python_Twisted, Python_Piddle
Perl Modules: Config::Natural, POSIX, DBI, IO::Socket::SSL, Log::Log4perl, Net::SSLeay, Math::Random
3. Centralized Case Installation
3.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
Next, login using SSH to each of the servers, copy the appropriate tar files over, and run the following commands to install the measurement service:
On the Root Beacon Server:
tar xzf RootBeacon.tar.gz cd RootBeacon/InstallScript chmod +x ontime_software_install_ubuntu64.sh ./ontime_software_install_ubuntu64.sh
On a Node Beacon Server:
tar xzf NodeBeacon.tar.gz cd NodeBeacon/InstallScript chmod +x ontime_software_install_ubuntu64.sh ./ontime_software_install_ubuntu64.sh
Note: CRON users should use "ontime_software_install_ubuntu64.sh" instead to install OTM on their Ubuntu x64 nodes.
3.2 Software Configuration
On the Root Beacon Server:
MySQL configuration
mysql -u root -p < BuildWebServicesDatabase.sql mysql -u root -p < BuildMeasurementDatabase.sql mysql -u root -p
At the mysql prompt, type
CREATE USER 'collector'@'%' IDENTIFIED BY '<collector password>'; GRANT ALL PRIVILEGES ON `Measurements` . * TO 'collector'@'%'; GRANT ALL PRIVILEGES ON `WebServices` . * TO 'collector'@'%'; exit
Note 1: Please change the <collector password> to a safe password.
Note 2: If remote access to MySQL on the Root Beacon is disabled, please open the port TCP/3306 in the firewall and follow the tutorial at http://www.cyberciti.biz/tips/how-do-i-enable-remote-access-to-mysql-database-server.html
Invocation options configuration
perl config_wizard.pl
Follow the steps as directed by the wizard script.
On a Node Beacon Server:
Invocation options configuration
perl config_wizard.pl
Follow the steps as directed by the wizard script.
Note: If you want to customize the parameters on invoking measurement tools, you can manually modify the "runtool.conf" which locates in the "NodeBeacon/etc" folder.
On the Web-portal:
Login to the OnTimeMeasure Researcher Web-portal and provide the Slice RSpec information.
3.3 Software Invocation
On the Root Beacon Server:
Go to "RootBeacon/RootScheduler/" and run
screen /opt/graphite/bin/run-graphite-devel-server.py /opt/graphite
If no error is reported, press '<CTRL>+a, c' sequence to open a new blank command window.
perl file_server.pl
If no error is reported, press '<CTRL>+a, c' sequence to open a new blank command window.
perl action_script.pl
If no error is reported, press '<CTRL>+a, c' sequence to open a new blank command window.
cd ../Collector/ perl collector.pl
If no error is reported, press '<CTRL>+a, d' sequence in the SSH window to keep the service running in the background.
On a Node Beacon Server:
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.
perl node_scheduler.pl
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 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>