| 1 | [[PageOutline]] |
| 2 | |
| 3 | = ORBIT Project Status Report = |
| 4 | |
| 5 | Period: 1Q09 |
| 6 | == I. Major accomplishments == |
| 7 | |
| 8 | === A. Milestones achieved === |
| 9 | |
| 10 | === B. Deliverables made === |
| 11 | We have achieved the following deliverables in this quarter: |
| 12 | a) Extend OMF to support multiple heterogeneous testbeds, anticipating GENI control framework structures where possible, and integrate into your testbeds. (6mo)[[BR]] |
| 13 | |
| 14 | b) Extend OMF interfaces and software to support mobile testbeds by: distributing experiment scripts to mobile nodes; providing local caching of experiment results during disconnection; and by executing experiment actions at predefined points in time (timebased orchestration). (8 mo)[[BR]] |
| 15 | |
| 16 | e) Establish OMF operating environment for your stationary and mobile testbeds, verify with experiments, and demo at a GEC. (6-12mo) [[BR]] |
| 17 | Deliverable b) was achieved early, in time for the GEC demo. |
| 18 | |
| 19 | == II. Description of work performed during last quarter == |
| 20 | |
| 21 | === A. Activities and findings === |
| 22 | Work on the three milestones listed above culminated in a demonstration of a wireless throughput |
| 23 | measurement experiment on a vehicular testbed at the recent GEC. The experiment measures |
| 24 | throughput between a Wifi interface inside the vehicle and a stationary access point located inside |
| 25 | the Winlab building as the vehicle moves. A second Wifi connection is used for control |
| 26 | (experiment configuration and measurement data). The experiment script is installed over this |
| 27 | control link in the vehicle at the start of the experiment. When the control connection becomes |
| 28 | disconnected during the experiment, results are cached in the vehicle, and the experiment |
| 29 | proceeds as governed by the time-orchestrated experiment script. When the control connection is |
| 30 | reestablished, the cached data is uploaded into the OMF measurement repository. |
| 31 | |
| 32 | The same experiment script can also be executed on the stationary ORBIT testbed or the |
| 33 | stationary testbed at NICTA. Thus, this demonstration showed OMFs capability to support |
| 34 | multiple heterogeneous testbeds. |
| 35 | |
| 36 | We have also made progress towards the following deliverables:[[BR]] |
| 37 | |
| 38 | '''Integrating OMF with WIMAX Basestation'''[[BR]] |
| 39 | The GEC demonstration also included a preliminary integration with the Wimax project, by |
| 40 | showing a video transmission over a Wimax link within the same experiment. We are now |
| 41 | working to provide direct OMF interfaces to control basestation settings from OMF experiment |
| 42 | scripts.[[BR]] |
| 43 | |
| 44 | '''Providing L2 connectivity to ORBIT'''[[BR]] |
| 45 | The missing fiber link between the Rutgers Food Science building and the Route 1 fiber corridor |
| 46 | (~1 mile) will be provisioned by Jun 30. We will be creating a 1 Gig lambda for Winlab in July to |
| 47 | our current location at 401 Broad Street in Philly on the 9th floor. From what we've heard to date |
| 48 | GENI is not using the 10Gig Wave, but are using the general Internet2 network so we should be |
| 49 | able to hand off directly to MAGPI in our current location.[[BR]] |
| 50 | In the meantime, we are ready to test L2 connectivity using a VPN over the excess capacity of |
| 51 | 400Mbps on Rutgers University's existing commodity feed to L2, if another testbed is available |
| 52 | for connection.[[BR]] |
| 53 | |
| 54 | '''Support and Collaboration'''[[BR]] |
| 55 | We provided input for the GENI security architecture draft, provided examples of ORBIT O&M |
| 56 | data and our current data format in use, and are continuously supporting external experimenters |
| 57 | on the stationary ORBIT testbed. |
| 58 | |
| 59 | We have also: |
| 60 | * Released an external website dedicated to OMF, its user community and its installation, utilization, and ongoing development.. This website is located at: http://www.mytestbed.net/ This website features an advanced traffic monitoring system (i.e. Google Analytics), which allows to monitor its impact. For example within the past 8 weeks, this website received an average of 75.4 (+/- 17.1) unique visits per week from an average of 31.9 (+/- 3.8) countries. |
| 61 | * Released a stable version of OMF (v1.2), available from the above website |
| 62 | === B. Project participants === |
| 63 | Marco Gruteser[[BR]] |
| 64 | |
| 65 | Max Ott[[BR]] |
| 66 | |
| 67 | Thierry Rakotoarivelo[[BR]] |
| 68 | |
| 69 | Ivan Seskar[[BR]] |
| 70 | |
| 71 | Tripti Singh[[BR]] |
| 72 | |
| 73 | === C. Publications (individual and organizational) === |
| 74 | None to report. |
| 75 | |
| 76 | === D. Outreach activities === |
| 77 | We have involved Tripti Singh, a Rutgers graduate student from an under-represented group, in |
| 78 | the design and development of the demonstration experiment shown at the recent GEC. |
| 79 | Specifically, she has lead the development of a Google Earth interface that visualizes the |
| 80 | experiment progress for demonstrations. |
| 81 | |
| 82 | === E. Collaborations === |
| 83 | The collaboration with UMass (ie. Deployment of OMF components on !DieselNet 'bricks') is |
| 84 | ongoing. Most of our resources in this quarter had been allocated to the realization of the |
| 85 | abovementioned committed deliverables (i.e. milestones Year1-b, and GEC4 demo). During the |
| 86 | next quarter we plan to port OMF to this platform and then run OMF on the moving !DieselNet |
| 87 | testbed. |
| 88 | === F. Other Contributions === |
| 89 | None to report. |