| 1 | [[PageOutline]] |
| 2 | |
| 3 | = ViSE Project Status Report = |
| 4 | |
| 5 | Period: 4Q08 |
| 6 | == I. Major accomplishments == |
| 7 | In the first quarter of the ViSE project we accomplished our initial set of bootstrapping |
| 8 | milestones and began work on the software and hardware infrastructure to complete |
| 9 | future milestones. We first provide details relating to the work behind achieving the two |
| 10 | 1st quarter milestones below. |
| 11 | |
| 12 | === A. Milestones achieved === |
| 13 | '''[1a]''' Assembly of three x86 sensor nodes. (2mo) Note: No budget allocated for hardware |
| 14 | development, which will be funded from other sources as needed. They are deployed on |
| 15 | the CS Building, UMass MA2 Tower, and Mount Toby, and are network accessible. |
| 16 | Also includes deployment of the !RayMarine radars at the three locations. (December |
| 17 | 1st). Completed. |
| 18 | |
| 19 | Milestone 1a was more challenging than anticipated due to the departure of a key staff |
| 20 | member (Brian Donovan) prior to the subcontract's start date. Brian's primary project |
| 21 | focus had been construction, integration, and maintenance of three modified !RayMarine |
| 22 | radars, one of three ViSE sensors with a "rich" set of programmable actuators. As a |
| 23 | result, other staff members learned both the software interface to the radar (e.g., through |
| 24 | an Adlink Data Acquisition Card and USB-to-PIC) as well as the details of radar to the |
| 25 | ViSE hardware platform (e.g., programmable PIC for radar control, data and control |
| 26 | connections, power and battery connections). While the learning curve had not been |
| 27 | planned for the 1st quarter, the results should ease the completion of future milestones |
| 28 | since much of the radar control software will have to be modified to complete future |
| 29 | milestones 1f and 1h in the fourth quarter of Spiral 1. |
| 30 | |
| 31 | Milestone 1a also required reconstructing nodes from a previous project (the Off-the-Grid |
| 32 | radar project) to accommodate the anticipated sharing and "deeply programmable" nature |
| 33 | of GENI. The modifications to the hardware platform were primarily the addition of a |
| 34 | more robust computing platform, two additional sensors called for by ViSE, and a |
| 35 | cellular backplane for out-of-band Operations and Management connections. The |
| 36 | computing platform includes a processor capable of running the Xen Virtual Machine |
| 37 | Monitor, which we will use to sliver node resources by allocating resources to virtual |
| 38 | machines created on-demand for user slices. The platform also includes a processor with |
| 39 | a higher clock-speed than the previous one (1.86Ghz) and more memory (2GB) and |
| 40 | storage (32GB Flash). ViSE adds both a weather station and a Pan-Tilt-Zoom video |
| 41 | camera to the sensor nodes in addition to the !RayMarine radar. Finally, our previous |
| 42 | experiences managing partially inaccessible node deployments motivated our integration |
| 43 | of a cellular backplane. We connected each main node to a Linux Gumstix Embedded |
| 44 | node with a connection to a commerical cellular network using a serial GPRS modem. |
| 45 | The Linux Gumstix includes both serial connections (for remote consoles) and wired |
| 46 | Ethernet connections to the main node and is capable of powering the main node using |
| 47 | Wake-On-Lan. At present, we are prototyping this backplane functionality on just the CS |
| 48 | Building ViSE node, but have found it useful thus far. |
| 49 | |
| 50 | In addition to deploying these nodes, we have also set up a testing environment in our lab |
| 51 | with an identical node and sensors attached, including a deconstructed (and nonradiating) |
| 52 | radar for testing. The testing environment will prove useful for future software |
| 53 | development (Milestons 1f and 1g). Finally, we documented each component of the |
| 54 | hardware platform for the GENI Substrate Catalog and forwarded it to John Jacobs at his |
| 55 | request. |
| 56 | |
| 57 | '''[1b]''' Field deployment of three sensor nodes; native non-virtualized drivers; software |
| 58 | testing. (January 1st). Completed. |
| 59 | |
| 60 | We have field deployed the nodes constructed in milestone 1b, and installed a base image |
| 61 | that includes the 3.2 version of Xen as well as the appropriate drivers for each sensing |
| 62 | device and wireless/wired card. Since the driver for the PCI9812 Adlink Data |
| 63 | Acquisition Card did not run under recent versions of !XenLinux (2.6.18) we modified the |
| 64 | source of the driver to support these; additionally, we obtained the most recent driver |
| 65 | from Adlink under a new NDA and are currently testing its compatibility with Xen in the |
| 66 | lab. Additionally, since the development of the base image is a tedious process we |
| 67 | heavily documented it on the ViSE Trac Web Site (http://vise.cs.umass.edu). |
| 68 | The documentation should prove useful to both the project, by preventing unnecessary |
| 69 | work in replicating configurations/images, and users, by providing a detailed description |
| 70 | of the node's foundational software layer (similar, in principle, to the Substrate Catalog |
| 71 | for documenting GENI hardware). Additionally, we also set up an initial |
| 72 | Trac web site and SVN repository for ViSE related software. The initial import into the |
| 73 | SVN repository includes the drivers and firmware for the radar and a framework for |
| 74 | developing Xen-compatible device drivers for each sensing device. In addition to |
| 75 | installing the base image we have codified and documented appropriate settings for |
| 76 | the wireless network card to communicate over long distances via 802.11b. |
| 77 | |
| 78 | '''Milestones in Progress'''[[BR]] |
| 79 | The next major milestone for ViSE Spiral 1 is 1b: Initial Shirako/ORCA integration. Xen |
| 80 | and Shirako software running on three sensor nodes, non-slivered, no radar control via |
| 81 | Xen by February 1st. We are well-positioned to complete this milestone at the present |
| 82 | time. We have a test deployment of Orca running in our lab, and the base software image |
| 83 | completed for Milestone 1b is compatible with Orca's existing framework for creating |
| 84 | and managing slices of Xen VMs. One minor modification to Orca is also necessary to |
| 85 | complete the milestone since Orca's existing codebase assumes a fully connected |
| 86 | topology (i.e., the management authority server assumes connectivity to any nodes in the |
| 87 | physical substrate). Since our wireless mesh does not adhere to this assumption, we |
| 88 | require a mechanism for the management authority to communicate with interior mesh |
| 89 | nodes. Our initial plan is to augment Orca node managers to forward messages (at the |
| 90 | application-level) from the management authority into the mesh using pre-configured |
| 91 | static routing tables. |
| 92 | |
| 93 | Work for subsquent milestones is also underway. Milestone 1d is a demo at GEC4. We |
| 94 | plan to demo both the Orca control framework on ViSE, as well as the capabilities of |
| 95 | radar actuation. We have also begun development of Xen drivers (Milestone 1f and 1h) |
| 96 | for the Camera, Weather Station, and radar sensors. We hope to use the same basic |
| 97 | framework for each sensor, and, since both the Camera and Weather Station interfaces |
| 98 | are well-documented, we are focusing on these two sensors in the initial stages of the |
| 99 | development, while working on the radar in parallel. |
| 100 | |
| 101 | === B. Deliverables made === |
| 102 | The first quarter of the project resulted in three primary deliverables: the ViSE chapter of |
| 103 | the GENI Substrate Catalog, the ViSE presentation and poster at GEC4, and the ViSE |
| 104 | Trac website and SVN repository for posting software and documentation. Details on the |
| 105 | completion of these milestones is provided in the previous section. |
| 106 | |
| 107 | == II. Description of work performed during last quarter == |
| 108 | |
| 109 | === A. Activities and findings === |
| 110 | The primary work during the quarter, including our Activities and Findings, centered on |
| 111 | achieving the milestones described above. In addition to attending GEC4, we held |
| 112 | monthly Cluster D group meetings via teleconference. The first meeting centered on |
| 113 | finding out about each project's goals and substrate characteristics. The second meeting |
| 114 | focused on coordinating for GEC4, while the third meeting included a demo of the Orca |
| 115 | control framework and a discussion of how each project fits into that framework. In |
| 116 | addition, one of our research staff sat in on a teleconference for demonstrating the Orca |
| 117 | control framework to BBN staff, and provided input on how Orca may integrate with |
| 118 | ViSE as well as other Cluster D projects. |
| 119 | |
| 120 | === B. Project participants === |
| 121 | The primary PI is Prashant Shenoy. Co-PIs are Michael Zink, Jim Kurose, and Deepak |
| 122 | Ganesan. Research Staff is David Irwin. |
| 123 | === C. Publications (individual and organizational) === |
| 124 | No publications resulted from the 1st quarter of work; we are preparing work related to |
| 125 | the actuator virtualization in ViSE for submission in the next quarter. Once completed, |
| 126 | this document will be publicly posted on the ViSE Trac website as a UMASS technical |
| 127 | report. |
| 128 | === D. Outreach activities === |
| 129 | In the first quarter we had no significant outreach activities. |
| 130 | However, during the summer we held a seminar for REU Undergraduate |
| 131 | Students on the construction of ViSE nodes and sensors |
| 132 | === E. Collaborations === |
| 133 | We have been working closely with the DOME project in our cluster at UMass and with |
| 134 | the Orca-BEN project at Duke. We are planning to integrate the Orca control framework |
| 135 | before their official release data 6 months into Spiral 1, and, as noted above, envision |
| 136 | only minor obstacles to completion. Additionally, we aided DOME in setting up a prerelease |
| 137 | of the Orca control framework to experiment with before an official release. |
| 138 | Finally, at GEC3 we discussed integration with the Kansei project at Ohio St. |
| 139 | === F. Other Contributions === |