Changes between Initial Version and Version 1 of ViSE-3Q09-status

05/27/10 11:04:55 (12 years ago)



  • ViSE-3Q09-status

    v1 v1  
     3= “SHORT NAME” Project Status Report =
     5Period: “date”
     6== I. Major accomplishments ==
     7The fourth quarter of the ViSE project includes the following major accomplishments:
     8  * A successful demonstration at GEC5 in July. The demonstration showed virtualization of actuators for our !RayMarine radars using a single guest VM.
     9  * A re-submission of ViSE-related technology to NSDI on October 2nd, 2009. The submission, titled ”!MultiSense: Fine-grained Multipexing for Steerable Sensor Networks” includes experimentation with both PTZ cameras and radars.
     10  * Significant progress toward early milestones in Spiral 2. These milestones include complete Xen sensor slivering for multiple VMs due 11/16/09, complete integration of your testbed with broker in cluster clearinghouse, so that your testbed becomes federated with the other associated testbeds due 11/16/09, work with GPO and cluster projects to complete a plan for the setup of VLANs between testbeds, to be carried by Internet 2 (or NLR) backbone network between the testbeds due 11/16/09, and deliver a first release (v1.x) of your testbed and web-based experiment control software, with documentation, to the GPO
     11  * Significant collaborations with, and contributions to, our Cluster D peers through numerous email exchanges, video conferences, and in-person meetings.
     12  * A continuing collaboration with the University of Puerto Rico, Mayag¨uez (UPRM), as part of our outreach plan.
     13The rest of this document describes in detail the major accomplishments above.
     15=== A. Milestones achieved ===
     16We achieved the following milestones in the 4th quarter as specified in our original Statement-of-Work.
     17  * '''July 31st, 2009.''' Contingent upon availability of reference implementation of Shirako/ORCA at 6 months, import and then integrate.
     18ViSE is running the latest reference implementation of the Shirako/Orca codebase. Note that Milestone 1c (completed
     19February 1st, 2009) required ViSE to perform an initial integration of Shirako/Orca prior to an official
     20reference implementation being released. See that milestone for specific details related to the integration. Incorporating the latest reference implementation required only minor code porting. Additionally, as a result of the Orca-fest conference call on May 28th, the GENI Project Office and Cluster D set mini-milestones that were not in the original Statement of Work. These milestones are related to Milestone 1e, since they involve the particular instantiation of Orca that Cluster D will use. In particular, by June 15th, 2009, we upgraded our ORCA actors to
     21support secure SOAP messages. As part of this mini-milestone, Brian Lynn of the DOME project and the ViSE
     22project also setup a control plane server that will host the aggregate manager and portal servers for both the DOME
     23and ViSE projects. This server has the DNS name The server includes 4 network interface
     24cards: one connects to a gateway ViSE node on the CS department roof, one will connect to an Internet2 backbone
     25site (via a VLAN), one connects to the public Internet, and one connects to an internal development ViSE
     26node. During the Orca-fest and subsequent Cluster D meetings we set the milestone for shifting within the range
     27of August 15th, 2009 and September 1st, 2009.
     29  * '''July 31st, 2009.''' Complete Xen sensor virtualization.[[BR]]
     30We completed an initial research-grade implementation of sensor virtualization in Xen and released a technical
     31report that applies the approach to Pan-Tilt-Zoom video cameras. The technical report can be found on the web
     32at and is also attached to this milestone report. As detailed in our previous quarterly status report we have faced challenges in applying the same techniques to the Raymarine radars in the ViSE testbed because their drivers do not operate by default inside of Xens Domain-0 management domain. The problem affects other high-bandwidth I/O devices that use Xen, and is being actively worked on in the Xen community. As these problems are worked out, we have transitioned to using vservers as ViSEs preferred virtualization technology, and developed vserver handlers for Orca. We are also porting !MultiSense to work with vservers as well as with Xen; its modular design makes this port straightforward. Our demonstration at GEC5 in Seattle showed non-slivered VM access to radar control and data using vservers; once we complete our port of !MultiSense we will be able to support slivered access. A more detailed description of these Xen, vservers, and sensors in ViSE is available in the quarter 2 quarterly report for ViSE. Since releasing our technical report, we have improved the work and re-submitted it to the NSDI conference. The improved work, which includes experiments with steerable radars, is also attached to this report.
     33  * '''October 1st, 2009.''' Contingent upon available budget, provide a VLAN connection from your testbed to the Internet2.
     34In cooperation with OIT at UMass-Amherst we have provided a VLAN connection from our control plane server to an Internet2 point-of-presence in Boston. In an email dated September 28th, 2009 Rick Tuthill
     36of UMass-Amherst OIT updated us on the status of this connection, as follows. ”I was down at the CS building
     37finishing this link setup on Friday – I think there may have been some confusion in the network jack ordering as
     38there are only two network ports currently activated. The two existing ports that are ’live’ are room 218A jack
     392-2-4D and room 226 jack 2-2-9D. These two ports and all intermediary equipment are now configured to provide
     40layer-2 VLAN transport from these networks jacks to the UMass/Northern Crossroads(NoX) handoff at 300 Bent
     41St in Cambridge, MA. The NoX folks are not doing anything with this research VLAN at this time. They need
     42further guidance from GENI on exactly what they’re supposed to do with the VLAN. Also, once IP addressing
     43is clarified for this VLAN, we’ll need to configure some OIT network equipment to allow the selected address
     44range(s) to pass through. I have signed the MOU and will return a countersigned ’original’ to Brian Levine....Let
     45me know if there’s anything I can do to facilitate testing of this link in the next couple of days.”
     47We intend this VLAN connection to service both the ViSE and the DOME testbeds. Thus, as required by this
     48milestone, we have coordinated with OIT at UMass-Amherst to provide a VLAN connection from our testbed to
     49the Internet2 backbone network. In the coming year, we have committed to planning with our peers in Cluster
     50D and the GPO on how to best use this new capability. As part of this plan, and before we can send/receive
     51traffic on this link, we will discuss the roles and capabilities of Internet2 in forwarding our traffic to its correct destination. Attached is the signed Memorandum-of-Understanding (MOU) between UMass-Amherst OIT and the DOME/ViSE projects with respect to our use of this VLAN connection. As discussed in the MOU, OIT is providing the link free of charge for the first year for prototyping purposes, but charge a fee in subsequent years based on our usage.
     52  * '''October 1st, 2009.''' Virtualization of actuators using a single guest VM and demo.[[BR]]
     53We demo’d control of the radar’s actuators at GEC5 in Seattle in July using vservers. Our technical reports
     54report more detailed information on the nature of this control.
     56  * '''October 1st, 2009.''' Testbed available for public use within our cluster.[[BR]]
     57Our testbed is available for limited use within our cluster. We are soliciting a select group of users to allow us
     58to work out the bugs/kinks in the testbed and figure out what needs to be improved. The portal for our testbed is
     59available at Note that as we develop our sensor virtualization technology
     60we are initially allowing users to safely access dedicated hardware—the sensors and the wireless NIC. Right
     61now, we are targeting two types of users for our testbed. The first type is users that wish to experiment with longdistance
     62802.11b wireless communication. Long-distance links are difficult to setup because they require access to
     63towers and other infrastructure to provide line-of-sight. Our two 10km links are thus useful to outside researchers
     64working on these problems. There are a number of students at UMass-Amherst using the testbed to solve problems
     65in this area. The second type of user is radar researchers that can leverage our radar deployment. We are working
     66with students from Puerto Rico and other researchers in CASA to interpret and improve the quality of our radar’s
     67data and test them for detection algorithms. We are soliciting feedback from these users about what they need
     68to do on these nodes, and how the testbed can satisfy their needs. Note that our testbed interacts with a remote
     69Clearinghouse run by RENCI/Duke to facilitate resource allocation.
     70  * '''October 1st, 2009.''' Switch to remote Clearinghouse at RENCI/Duke [[BR]]
     71While not in our official list of milestones, Harry Mussman asked our Cluster to switch to using a remote
     72Clearinghouse by October 1st. We have made this switch. We first made use of a jail that we controlled at
     73RENCI/Duke to setup and test this Clearinghouse in mid-August, and on September 28th, 2009 sent email to
     74RENCI asking them to switch us over to their Clearinghouse.
     76'''Milestones in Progress'''[[BR]]
     77Below we list the milestones for quarter 1 of Spiral 2, as recently agreed upon in our Spiral 2 Statement-of-Work.
     78  * '''November 16, 2009''' Complete Xen sensor slivering (multiple VMs).[[BR]]
     79We have made significant progress toward this milestone as detailed in our two technical reports. We are beginning
     80to port our existing Xen implementation to vservers.
     81  * '''November 16th, 2009.''' Complete integration of your testbed with a broker in the cluster clearinghouse, so
     82that your testbed becomes federated with the other associated testbeds. Demo functionality of your testbed
     83in this environment, including access from experiment control tools and service managers that are remote
     84from your testbed. [[BR]]
     85As detailed above, we have integrated our testbed with the broker at the remote Clearinghouse. Our plan is to demo
     86this portal and integration at the upcoming GEC.
     87  * '''November 16th, 2009.''' Work with GPO and cluster projects to complete a plan for the setup of VLANs
     88between testbeds, to be carried by Internet 2 (or NLR) backbone network between the testbeds.[[BR]]
     89Our status relative to Internet2 is detailed above. We are well-prepared to complete a plan for using our existing
     91  * '''December 1st, 2009.''' Deliver a first release (v1.x) of your testbed and web-based experiment control software, with documentation, to the GPO. [[BR]]
     92We are currently readying our code for release, and are in good position to satisfy this milestone.
     93  * '''January 1st, 2010.''' Best-effort installation of Pelham tower x86 sensor node (note: funded from other
     94sources), to include meteorological sensors, radar (if licensed), communications, computing. No camera. If
     95Pelham node is problematic, optional rapidly-deployed node replaces Pelham node.[[BR]]
     96We have ordered the parts for the Pelham node and coordinated with the Massachusetts Department of Conservation
     97and Recreation to setup the node. We are pushing to bring the node up this fall before the winter snow.
     99=== B. Deliverables made ===
     100The third quarter of the project includes work toward a number of deliverables. These deliverables include the
     101ViSE demonstration and poster on GEC5 on July 20th, 2009 in Seattle. Along with Brian Lynn and Ilia Baldine,
     102we aided in drafting documentation and code for other Cluster D projects, such as !KanseiGenie, that they can use as
     103templates for integrating their own testbed. We have also contributed to GPO and Cluster-wide GENI discussions.
     105== II. Description of work performed during last quarter ==
     107=== A. Activities and findings ===
     108The primary work during the quarter, including our Activities and Findings, centered on achieving the milestones
     109described above and making progress toward our initial Spiral 2 milestones. In addition to attending GEC5, we
     110held monthly Cluster D group meetings via teleconference.
     111=== B. Project participants ===
     112The primary PI is Prashant Shenoy. Co-PIs are Michael Zink, Jim Kurose, and Deepak Ganesan. Research Staff is
     113David Irwin. Navin Sharma, a graduate student, is also contributing to the project and is the primary author of the
     114ViSE-related submission currently under review.
     115=== C. Publications (individual and organizational) ===
     116We submitted our research on sensor virtualization with Xen to !SenSys. Although the paper was well-reviewed it
     117was not selected for publication. We have improved the work and re-submitted it to the NSDI conference.
     118=== D. Outreach activities ===
     119We are continuing our discussions with UPRM about integrating with their student radar testbed project. We have
     120bi-weekly meetings with the Student Testbed Project at UPRM. Jorge Trabal, the primary student working on the
     121UPRM project, is visiting UMass-Amherst until he completes his Ph.D. The testbed project at UPRM has the same
     122origins as the ViSE testbed, and thus many of the components are the same. However, while ViSE is focused on
     123the virtualization aspect of the testbed, the UPRM team is focused on improving the data provided by its radar.
     124Thus, the two projects are complementary. We are discussing with Jorge the best way to leverage their improved
     125radar data, as well as the potential for integration with ViSE in the future.
     126=== E. Collaborations ===
     127We collaborated with other Cluster D projects significantly during the quarter. First, we setup and maintained for both the ViSE and DOME projects. We also aided with the integration with RENCI’s Clearinghouse for both ViSE and DOME. Additionally, we had numerous email exchanges on the Orca user mailing list about the intricacies of integration and setup. We also setup to connect to the Internet2 VLAN
     129connection. ViSE also participated in the review of GPO documents on Experiment Services and Workflow.
     130=== F. Other Contributions ===