wiki:OnTime-Installv1

Context Navigation

Version 31 (modified by zhu.249@osu.edu, 14 years ago) (diff)
--

OnTimeMeasure-GENI Installation Document

Prasad Calyam, Kunpeng Zhu
Sep 17, 2010

Software License: 'GENI Project License (GPL)'

1. Getting Started

This document describes the installation, configuration and usage of OnTimeMeasure-v1.0, 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 a ProtoGENI/Emulab and PlanetLab user to register, create and monitor experiment slices on a geographically distributed resources in the GENI facility.

Before proceeding further, we highly recommend reading the Early Experimenter Tutorial.

2. OnTimeMeasure Installation:

2.1 Requirements

The OnTimeMeasure software package has the following requirements:

Operating System: Fedora

Pre-requisite Software: MySQL, Graphite, Perl, Python, Iperf, Ruby, Bwctl-server, Bwctl-client, Cairo, Python_Twisted, Python_Piddle, perl-CPAN

Perl Modules: Config::Natural, POSIX, Sys::HostIP, DBI, IO::Socket::SSL, Log::Log4perl, Net::SSLeay, Math::Random, YAML, HTTP::Daemon

Note: The Pre-requisite Software and Perl Modules installation is handled by the scripts delivered in the OnTimeMeasure-v1.0 package. See following sections for details.

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 Emulab Network Testbed

2.2 ProtoGENI Slice Creation and Configuration

Note: To obtain detailed information about ProtoGENI slice creation, please refer to the 'ProtoGENI Tutorial'

To create a ProtoGENI slice, we need to define the corresponding 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>

To check availability of nodes to include in an RSpec, please refer to the 'ProtoGENI Flash Interface'.

2.3 Sliver Creation and Management

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>

2.4 Software Installation

Download the OnTimeMeasure-v1.0.tar.gz release package at http://ontime.oar.net/download/OnTimeMeasure-v1.0.tar.gz.

In case you have not received the download information, please email - Prasad Calyam

Once you have downloaded the tar file, untar/unzip to see that OnTimeMeasure-v1.0.tar.gz 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 setup the measurement instance environment:

Centralized/Distributed Case:

On the Root Beacon Server:

Software installation

tar xzf RootBeacon.tar.gz
cd RootBeacon/InstallScript
chmod +x ontime_software_install.sh
./ontime_software_install.sh

MySQL Initialization

mysqladmin -u root password '<new-password>'

On a Node Beacon Server:

Software installation

tar xzf NodeBeacon.tar.gz
cd NodeBeacon/InstallScript
chmod +x ontime_software_install.sh
./ontime_software_install.sh

2.5 Software Configuration

Centralized Case:

On the Root Beacon Server:

MySQL configuration

cd RootBeacon/InstallScript
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 use the <collector password> provided as part of the Slice information at Step 2 in the Researcher Web-portal.

Note 2: If remote access to MySQL on the Root Beacon is disabled, please open the port TCP/3306 and follow the tutorial at http://www.cyberciti.biz/tips/how-do-i-enable-remote-access-to-mysql-database-server.html

Graphite Configuration

Initialize the graphite:

cd /opt/graphite/webapp/graphite/
sudo python manage.py syncdb

Note: For the first time execution, you will be prompted for creating a 'root' user.

Run the graphite and carbon daemons

screen
cd /opt/graphite/
python bin/carbon-cache.py start
sudo chmod -R 777 /opt/graphite/storage
/opt/graphite/bin/run-graphite-devel-server.py /opt/graphite

Then open <root_beacon_ip_address>:17280 in browser. If no error is reported, press '<CTRL>+a, d' sequence in the SSH window to keep the service running in the background.

Root Beacon invocation options configuration

cd RootBeacon/InstallScript
perl config_wizard.pl

Follow the steps as directed by the wizard script.

On a Node Beacon Server:

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:

Distributed Case:

On a Node Beacon Server:

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:

2.6 Software Invocation

Centralized Case:

On the Root Beacon Server:

Go to "Collector/" and run

screen
perl collector.pl

If no error is reported, press '<CTRL>+a, c' sequence to open a new blank command window. Then, go to "../RootScheduler/"

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, d' sequence in the SSH window to keep the service running in the background.

On a Node Beacon Server:

Go to 'Datagen/' 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.

Distributed Case:

On a Node Beacon Server:

Go to '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.

Download in other formats:

Plain Text