Custom Query (1408 matches)

The ViSE project will demonstrate sensor control using the Orca control framework, sensor scheduling, and our progress toward sensor virtualization. The specific demonstration description below is subject to some changes/simplifications, depending on our progress near the end of March. The primary demonstration is #1 below, while #2 and #3 will be subject to progress at that point.

Requirements: We will require 2 A/C outlets for plugging in two sensors and two laptops (we will bring a power strip ourselves). We will need table space for our equipment and tack space if a poster is required for GEC4. We will also need wireless access for #3 below. We would like to be placed next to the Orca/BEN project from RENCI/Duke. We would prefer a large monitor to plug our laptop(s) into, as we will not be transporting a monitor ourselves, but this is not required.

1. We will bring a Pan-Tilt-Zoom (PTZ) video camera and a DavisPro weather station to GEC4, to act as example sensors (Note: our radars are too large to transport to Miami). We will conduct the demonstration on a single laptop with the PTZ video camera connected via Ethernet. The laptop will be a "GENI in a bottle": we will run 4 VMware virtual machines on the laptop, each of which corresponds to 1 GENI Aggregate Manager (or Orca site authority) and GENI Clearinghouse (or Orca broker), 2 GENI Experiments, and 1 GENI component that the aggregate manager controls. The GENI component will be a VMware virtual machine that runs an instance of the Xen virtual machine monitor inside of it. The GENI Aggregate manager will be empowered to create slivers as Xen virtual machines on the GENI component (since we have only a single component in the demonstration, these slivers correspond to a slice). The Experiments will communicate with the Clearinghouse and Aggregate manager using SOAP network communication.

Importantly, the GENI component VM will be able to control access to the PTZ camera by attaching and detaching virtual network interfaces to/from experiment VMs. Each experiment will request a slice composed of a single Xen VMM sliver with a reserved proportion of CPU, memory, bandwidth, etc. The experiments will then compete for control of, and access to, the PTZ camera by requesting a lease for it from the Clearinghouse and directing the Aggregate Manager to attach it (in the form of a virtual network interface) to their sliver---only a single Experiment can control the camera at one time so the Clearinghouse must schedule access to it accordingly. We will use the default Orca web portal to display the process, and the PTZ camera web portal on both experiment's to show the status of the camera.

2. We will also show our progress on true sensor virtualization in the Xen virtual machine monitor. In the case of the camera, the "virtualization" takes the form of permitting full access to the camera by one, and only one, VM through its virtual network interface. We are currently integrating virtualized sensing devices into Xen's device driver framework. We will show our progress towards "virtualizing" a Davis Pro weather station that physically connects to a virtual USB port. Our initial goal along this thread is to have the Davis Pro software run inside of a Xen VM on top of a virtual serial driver that "passes through" requests to the physical device. This is the first step towards our milestones near the end of the year for sensor slivering.

3. While the above demonstrations will be local, we will also have access to our testbed in Massachusetts, running the Orca software, available, as per our milestone in February. We also hope to demonstrate the basic capabilities of our weather radar remotely, using a standard reflectivity map.

We plan to demo some new features of the ProtoGENI control framework at GEC4. We will need table space, a power outlet, and Internet access.

The demo will take place on a laptop, so it would be ideal if the table space were elevated so that it's easily viewable while standing. This is not required, however.

Wired Ethernet would be preferable, simply for reliability reasons.

The demo will involve intermittently receiving files of a few MB, so reasonable bandwidth (at least fast DSL speeds) is desirable.

We plan to demo the initial integration of Programmable Edge Node with Emulab/ProtoGENI control framework. We will need table space, a power outlet, and Internet access for two laptop PCs.

The demo will take place on a laptop, and some background admin work will happen on the other laptop. We prefer wired network connection for reliability purpose. We don't require significant bandwidth.