= !OnTimeMeasure-GENI Installation Document = '''Prasad Calyam, Weiping Mandrawa, Kunpeng Zhu'''[[BR]] '''May 31, 2010'''[[BR]] ''Software License:'' [http://www.geni.net/wp-content/uploads/2009/02/geniprojlic.pdf ''GENI Project License (GPL)''] [[BR]] == 1. System Requirements: == A. Operating System: Fedora[[BR]] B. Software: MySQL, Graphite, Perl, Python, Iperf, Ruby, Bwctl-server, Bwctl-client, Python_Twisted, Python_Piddle, perl-CPAN[[BR]] C. Perl Modules: Config::Natural, POSIX, Sys::HostIP, DBI, IO::SOCKET::SSL, Log::Log4perl:Net::SSLeay, Math::Random, YAML[[BR]] The Prerequisites Software and Perl Modules installation is handled by the scripts delivered in the OnTimeMeasure-GENI-v1.0 package. See following sections for details. == 2. !OnTimeMeasure-GENI Installation: == !OnTimeMeasure-GENI 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 [http://ontime.oar.net ''OnTimeMeasure researcher web-portal''] enables a ProtoGENI/Emulab user to register, create and monitor experiment slices on a geographically distributed backbone encompassing Internet2 resources with experiment nodes at Kansas, Washington and Utah locations. An example deployment of centralized !OnTimeMeasure-GENI could feature 1 Root Beacon at Kansas, and 2 Node Beacons at Washington and Utah locations, respectively. An example deployment of distributed !OnTimeMeasure-GENI could feature Node Beacons at Kansas, Washington and Utah locations, respectively. === 2.1 ProtoGENI Slice Creation and Configuration === '''Note:''' To obtain detailed information about ProtoGENI slice creation, please refer to the [https://users.emulab.net/trac/protogeni/wiki/TutorialNew ''ProtoGENI Tutorial''][[BR]] 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: {{{ 1000000 1000000 }}} To check availability of nodes to include in an RSpec, please refer to the [https://www.emulab.net/nodecontrol_list.php3?showtype=widearea&typefilter=pcpg,pcpg-i2 ''Emulab web-page'']. Note that you will need to have an Emulab account to access the web-page.[[BR]] === 2.2 Sliver Creation and Management === - Register a slice {{{ registerslice.py –n }}} - Create sliver inside slice {{{ createssliver.py –n }}} - Start sliver {{{ startsliver –n }}} - Check sliver status {{{ sliverstatus –n }}} Note: You may need to renew your sliver just after successful creation. For this, {{{ renewsliver –n