Custom Query (1408 matches)
Results (91 - 93 of 1408)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #106 | fixed | milestone 1f completion | ||
| Description |
Per 1Q09 QSR: As shown by our demonstration at GEC4, we have made significant progress toward completing Xen sensor virtualization and non-slivered control of radar sensor data. GEC4 showed a preview of this virtualization capability for our DavisPro weather station, and we have a working version of the capability for our PTZ camera in the lab. We are continuing these efforts in the third quarter. Code is being updated to the ViSE svn repository at http://vise.cs.umass.edu/svn. Per 7/31/09 report: We have completed an initial research-grade implementation of sensor virtualization in Xen and released a technical report that applies the approach to Pan-Tilt-Zoom video cameras. The technical report can be found on the web at http://www.cs.umass.edu/publication/details.php?id=1575 and is also attached to this milestone report. As detailed in our 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 Xen’s 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 ViSE’s preferred virtualization technology, and developed vserver handlers for Orca. We are also porting VSense 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 VSense 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. 2 |
|||
| #107 | fixed | Hold discussions with GMOC on security for initial data sharing | ||
| Description |
GMOC data sharing in Spiral 1 and in later spirals requires security design for access control and user authentication. Contribute to design and procedures established by GMOC for Spiral 1 and later work. |
|||
| #108 | fixed | Provide information on prototype clearinghouse and where/how it will operate. | ||
| Description |
Please add this information to the TIED wiki page(s). Milestone is late. |
|||
