Changes between Initial Version and Version 1 of GIR3.1_OnTimeMeasuraments

03/14/11 09:49:39 (11 years ago)



  • GIR3.1_OnTimeMeasuraments

    v1 v1  
     1= !OnTime Measuraments Evaluation =
     3On November 30, 2010 the '''!OnTimeMeasure v2.0''' !r524 software package was made available introducing the following features:
     51. !OnTimeControl module, a command-line tool used to perform all the measurement service functions between client-and-server currently being done interactively with researcher web-portal ( This tool provides capabilities for integration with experiment work-flow tools such as GUSH. It can be configured to work with or without the web-portal.
     72. Installation and configuration of !OnTimeMeasure were simplified. The entire installation and configuration can be completed within 5 minutes.
     93. New GENI OS platforms are supported, including both Fedora and Ubuntu 64bit OS. Also, !OnTimeMeasure has been integrated to work with the following GENI projects:
     10    a. [ OnTimeMeasure-ProtoGENI]
     11    b. [ OnTimeMeasure-PlanetLab]
     12    c. [ OnTimeMeasure-CRON]
     13    d. [ OnTimeMeasure-InsTools]
     154. Measurement Service status reporting support, which allows checking item-by-item both on the Web-portal and by the command-line !OnTimeControl tool.
     175. Stability has been improved with many miscellaneous bug fixes.
     19A second version was made available on January 13, 2011 the '''!OnTimeMeasure v2.0''' !r536 software package was made available new version delivered a PHP parse error resolution.  This second version was successfully used to evaluate the new features.
     22= On Time Measurement Tools Findings =
     24Initial evaluation focused on documentation for !OnTimeControl module.  Documentation for installation and configuration were initially vague. A second version was much more detailed an provided enough information to install and use the modules.  A [ tutorial] was very useful in providing an overview of each component along with their architecture.  The evaluation for the January 13th version was completed, some minor documentation changes are outstanding and will be verified in the next planned version which integrates !OnTimeMeasure tools with GUSH.
     27= On Time Measurement Tools How-to =
     29Initially reviewed the documentation for the new documents:
     30 * [ OnTimeControl User Manual]
     31 * [ OnTimeBeacon Installation] and later [ Updated OnTimeBeacon Installation] manual.
     32 * [ OnTimeBeacon User Guide]
     34Initial review of documents listed did not provide enough information to explain how the new modules fit into the existing set of tools.  Found that a good overview of the entire !OnTimeMeasure system is available in the [ tutorial] which helped in understanding and planning the installation.
     36Initial installation found a php parsing error which resulted in updated installation and new version of !OnTimeBeacon.
     38Second version was installed and successfully configure to show the web portal using the instructions provided. Using this version was able to install the !RootBeacon, and !NodeBeacons as instructed in the [ Install Procedure].  This is not being capture here, because the [ Install Procedure] captures all required installation, configuration and run-time for the !RootBeacon and !NodeBeacon Nodes.  Also the nodes used for !OnTimeControl and !OnTimeBeacon were gpolab nodes, while the nodes used as !RootBeacon and !NodeBeacon were emulab nodes.  One issue was found with this version which was due to missing process in the start-up instructions.
     40== !OnTimeControl How-to ==
     42After unpacking the !OnTimeControl-v2.0-build524.tar.gz file the following steps were executed:
     441. Copied the file config_example.yaml to config.yaml and mofied to capture my nodes and their role, here is
     45   the content of the config.yaml used for testing:
     47  connection: direct
     48  ##################################################
     49  # Setup for direct connection
     50  ##################################################
     51  root_beacon:
     52  db_user: collector
     53  db_pwd: collector
     55  nodes:
     56  - name: pc315
     57    IP:
     59  - name: pc299
     60    IP:
     632. Once the config.yaml is in place, it is possible to check the service status for the specified nodes:
     65  $ python
     66  {'root_scheduler': 'OK', 'graphite': 'OK', 'file_server': 'OK', 'collector': 'OK...'}
     683. To define measurement task, modify the measurement.yaml file.  Following is the measurement.yaml used for testing:
     70pattern: Periodic
     73- source: pc315
     74  destination: pc299
     75  metric: [Throughput, RoundtripDelay, Jitter, RouteChanges]
     77- source: pc299
     78  destination: pc315
     79  metric: [Jitter,RoundtripDelay, Throughput, RouteChanges]
     824. To enable the measurement tasks defined in the that are configured in the measurement.yaml file, the following are run:
     85  $ python ./ -c measurement.yaml
     86  All old tasks cleared
     87  8 new tasks added
     88  You have to restart the measurement service to put them into effort
     89  $ python stop
     90  stopped
     91  $ python start
     92  running
     94  At this point measurements are being collected on the !Nodebeacons and will be available for queries.
     964. A query can be used to download the details for the specified options, following are example queries:
     98$ python ./ -f "2011/01/31 14:16:40"  -t "2011/02/01 16:16:40"  -s pc315 -d pc299 -m RoundTripDelay -r TimeSeries
     100$ python ./ -f "2011/01/31 14:16:40"  -t "2011/02/01 16:16:40"  -s pc315 -d pc299 -m Throughput -r TimeSeries   
     103  The above result in files downloaded to the directory where the query is issued.  The file downloaded files contains results for the specified time frame:
     105$ more 20110201162227_Ping_RoundTripDelay.txt
     1062011-02-01 13:20:44     0.285
     1072011-02-01 13:48:43     0.429
     1082011-02-01 14:20:43     0.262
     1092011-02-01 14:48:43     0.508
     1102011-02-01 15:20:43     0.412
     1112011-02-01 15:48:44     0.453
     113$ more 20110201162406_IperfTcp_Throughput.txt
     1142011-02-01 13:18:43     94.4
     1152011-02-01 14:18:44     94.5
     1162011-02-01 15:18:43     94.4
     121== !OnTimeBeacon How-to ==
     1231. Evaluated included both Fedora and Ubuntu platform. Prerequisite for standard LAMP Severs was met by following suggested documentation for [ Fedora LAMP] and [ Ubuntu LAMP].
     1252. Install pre-requisite software for Fedora:
     127sudo yum install sendmail curl phpMyAdmin
     129For Ubuntu
     131sudo apt-get install sendmail curl php5-curl phpmyadmin
     134'' Note: ''
     135Sendmail package is not required, other package used in its place, Postfix on ubuntu''
     1373. Initialize Database by opening a browser session to <server_IP>/phpmyadmin and logging in as root. Select "Import" panel and create a new database named "!OnTimeMeaure", and then import the "!OnTimeMeasure.sql" which locates in the "install" folder.
     139'' Note: ''
     140On Ubuntu node was not able to access phpmyadmin the following  was added to the Apache configurations /etc/apache2/apache2.conf:
     141''  "Include /etc/phpmyadmin/apache.conf" ''
     1444. Restart the http server:
     147 $ sudo /sbin/service httpd restart
     1505. Unpacked the !OnTimeBeacon-v2.0-build536.tar.gz file and copied its contents to /var/www, then in the /var/www directory renamed the file "config_example.php" to "config.php" and modified to contain settings for the newly installed web portal:
     152// ** MySQL ** //
     153define('DB_NAME', 'OnTimeMeasure');
     154define('DB_USER', 'root');
     155define('DB_PASSWORD', 'XXXX');
     156define('DB_HOST', 'localhost');
     158// ** Email noticification **//
     159define('MAIL_SENDER', 'Ontime Admin <>');  // Sender information showed in the notification emails
     160define('ADMIN_EMAILS', ''); // Administartor emails. Notification emails will be sent to the list when things appen in the web portal
     1636. User can now connect to the portal at http://hostname/UserLogin.php (where hostname is the !OnTimeBeacon nodes).
     1657. Once connected user can define and start monitoring.  This is not changed since the GIR2.1 [ OnTime evaluation] so it is not captured here.