OnTimeMeasure Integration with Gush Prasad Calyam, Ph.D. (PI) Tony Zhu (Software Programmer) Alex Berryman (REU Student) GEC10 Selected Project Highlights Session March 15 th 2011

Topics of Discussion OnTimeMeasure Overview Gush Overview OnTimeMeasure-Gush User Workflow Integration Details 2

OnTimeMeasure Overview Goal: Provide GENI community with capabilities for provisioning on- going and on-demand measurement requests –Used in forecasting, anomaly detection, and fault-location diagnosis in GENI experiments and GENI operations Outcomes: –Software to perform centralized and distributed measurement orchestration and provisioning of measurements Centralized orchestration for continuous monitoring, persistent measurements storage and processed network measurement feeds Distributed orchestration for on-demand (real-time) measurement requests without need for persistent measurements storage –Measurement service that enables users to utilize OnTimeMeasure software in GENI experiments Registers users, slices, maintains meta-data, and allows user control of measurement service functions –Researcher Web-portal – for interactive user control of measurement servicehttp://ontime.oar.net –Command-line tools for measurement service control automation 3

OnTimeMeasure Architecture 4

Gush Overview Gush runs on a user desktop and executes commands on Client nodes in a GENI Slice The application description is written in an XML format with following specs: –Web addresses of software packages –List of target clients –Commands to be executed Two configuration files are required in Gush (filled in using a helper script): 1.Directory.xml: defines where to locate resources during execution of experiment  Gush queries PlanetLab database about user slice and auto populates the Directory.xml file 2.Gush.prefs: define working directory and client prefix Source: Gush project website - 5

Advantages of OnTimeMeasure-Gush Integration Improves Experiment Measurements in Classroom: –Students can instrument/query/analyze active and passive measurements within GENI using their familiar Gush interface –Get on-demand plots of measurement time series results of their experiments with simple commands in Gush Don’t need to teach students GNUPlot Eases Installation of OnTimeMeasure: –Configure once and re-use in slices using their familiar Gush interface –Login and install on a number of nodes from user desktop Gush takes care of ProtoGENI/PlanetLab authentication Improves Automation, Scalability and Security of OnTimeMeasure : –Identical configuration steps on Node Beacons can be done in parallel across large number of nodes –GENI experimenter can securely script the request/management/query of OnTimeMeasure measurements through Gush 6

User Workflow (ProtoGENI or PlanetLab Aggregates) 1.User creates an experiment slice using ProtoGENI or PlanetLab control framework tools –For ProtoGENI slice creation, see –For PlanetLab slice creation, see User registers at the “Researcher Web-Portal” ( 3.User installs OnTimeMeasure measurement instance in experiment slice –Slice RSpec should include reservation of any required measurement resources –Node/Root Beacons need to be installed as slivers based on the instructions provided in Step-1 for the specific aggregate 4.User installs Gush and uses OnTimeMeasure xml files to: i.Submit measurement requests ii. Control the measurement service iii. Query measurement data For details, see - See Demo of OnTimeMeasure-Gush at GEC10 Project Demo & Networking Event… 7

Deployment Steps for OnTimeMeasure-Gush ProtoGENI/PlanetLab slice must be created using an RSpec file or using graphical interfaces XML file of the application description must be created with at least two parts: –Commands to be executed only on the Root Beacon –Commands to be executed on all of the Node Beacons Description of the slice resources must be written in directory.xml Gush.prefs must be configured correctly as per Gush setup instructions Gush Controller Otm- deploy.xml Root Beacon Node Beacon Root Beacon directory.xml gush.prefs Node Beacon GENI Slice 8

OnTime Control (Stand-alone Mode) User installs OnTime Control on his/her desktop –Requires Python install –Manually configure slice topology in.yaml files User executes python scripts that query a SQL database of measurements on the Root Beacon –Requires root db user information Measurement result time-series files/plots are automatically downloaded into current directory on user desktop User Desktop OnTime Control Python Scripts Slice Topolgy.yaml files Root Beacon Root Beacon DB Node Beacon Node Beacon Node Beacon Node Beacon Node Beacon Node Beacon GENI Slice 9

OnTime Control (GUSH Integration mode) OnTime Control package resides on Root/Node Beacon; Gush is installed on user desktop Write a set of XML experiment files in the Gush format that interacts with the OnTime Control python scripts Gush topology description (directory.xml) is passed to the OnTime Control Output of the OnTime Control is a URL of a text/plot file containing the results of the measurement User Desktop OnTime Control Python Scripts Slice Topology Root Beacon Root Beacon DB Node Beacon Node Beacon Node Beacon Node Beacon Node Beacon Node Beacon GUSH Controller otm- control.xml directory.xml GENI Slice 10

Reference List OnTime Control Wiki – OnTimeMeasure-PlanetLab Wiki – OnTimeMeasure-ProtoGENI Wiki – OnTimeMeasure-Gush Wiki – 11

12 Thank you for your attention ! This material is based upon work supported by the National Science Foundation under Grant No. CNS Any opinions, findings, and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of BBN Technologies, Corp., the GENI Project Office, or the National Science Foundation.