Changes between Version 5 and Version 6 of Ticket #39
- Timestamp:
- 05/05/09 17:15:42 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #39 – Description
v5 v6 4 4 no radar control via Xen. Due February 1st, 2009. 5 5 [[BR]] 6 6 7 The Orca control framework comprises a set of three distinct actor servers that correspond to GENI Experiments, 7 8 Clearinghouses, and Aggregate Managers 1. GENI experiments correspond to Orca service managers, … … 11 12 an Orca site authority within the same Java virtual machine that communicate using local procedure calls. 12 13 [[BR]] 14 13 15 The Orca actor servers run on a gateway node connected to both the public Internet (otg.cs.umass.edu) and the 14 16 sensor node on the roof of the UMass-Amherst CS department. The sensor node on the UMass-Amherst roof, in … … 18 20 with the Orca node agent to instantiates virtual machines for experiments. 19 21 [[BR]] 22 20 23 Each node is primed with the software necessary to create Xen virtual machines and sliver their resources. The 21 24 local storage is a 32gb flash drive partitioned using logical volume manager. The Orca node agent snapshots a … … 23 26 tc is installed on each node to shape and limit each experiment’s network traffic. 24 27 [[BR]] 28 25 29 Using the default Orca web portal, users are able to login and request slices on the ViSE testbed. Currently, 26 30 only the sensor node on the CS roof is accessible by end-users. We have decided to wait until the end of winter to … … 28 32 We expect to access them in early-to-mid April depending on the weather and the snow melt. 29 33 [[BR]] 34 30 35 In addition to the software to support Orca, each node has the appropriate foundation software/drivers to 31 36 operate the sensors, wireless and wired NICs, an attached Gumstix Linux embedded control node, and a GPRS … … 37 42 images at http://vise.cs.umass.edu. 38 43 [[BR]] 44 39 45 The milestone is a pre-cursor to our sensor virtualization work. While users are able to create slices composed 40 46 of Xen virtual machines bound to slivers of CPU, memory, bandwidth, and local storage, they are not able to access