| | 1 | = ProtoGENI Project Quarterly Report for 4Q 2008 = |
| | 2 | |
| | 3 | == I. Major accomplishments == |
| | 4 | |
| | 5 | === A. Milestones achieved === |
| | 6 | |
| | 7 | Year 1(g): Gave a demo of progress early, at GEC #3 |
| | 8 | |
| | 9 | === B. Deliverables made === |
| | 10 | |
| | 11 | Documentation of design decisions and plans up at http://www.protogeni.net/ |
| | 12 | |
| | 13 | Release of Emulab software, including early versions of ProtoGENI extensions, made under the AGPLv3 in July (before contract awarded) |
| | 14 | |
| | 15 | Early RSpec prototype (still in progress) released at: http://www.protogeni.net/trac/protogeni/wiki/RSpec |
| | 16 | |
| | 17 | Early credential and ticket formats (still in progress) released at: http://www.protogeni.net/trac/protogeni/wiki/Authentication |
| | 18 | |
| | 19 | == II. Description of work performed during last quarter == |
| | 20 | |
| | 21 | === A. Activities and findings === |
| | 22 | |
| | 23 | In our role as a control framework, most of the activity billable this quarter |
| | 24 | to this contract has been integration, collaboration (see below), and running |
| | 25 | of a clearinghouse and aggregate component managers. We have brought up a |
| | 26 | clearinghouse and two aggregate component managers at Utah. These are by no |
| | 27 | means complete, but represent a strong start. We have lined up four external |
| | 28 | sites to host ProtoGENI edge nodes. Two of these sites have been running for |
| | 29 | over a moth, and the other two will come up after the holidays. |
| | 30 | |
| | 31 | Under separate NSF funding, we have done extensive development on ProtoGENI, |
| | 32 | including: |
| | 33 | |
| | 34 | Work on the aggregate component manager frontend to the Emulab management software |
| | 35 | |
| | 36 | Building software to run a clearinghouse |
| | 37 | |
| | 38 | Building software to create and validate user identities, credentials, and tickets |
| | 39 | |
| | 40 | Enabling federation between sites running Emulab software, using the ProtoGENI APIs |
| | 41 | |
| | 42 | The last is particularly important, as it will be a primary method for |
| | 43 | integration with other cluster members who run Emulab instances (which is |
| | 44 | nearly all of them.) An early version of this federation (of aggregates) has been tested within |
| | 45 | Utah, using separate Emulab instances, but remains to be deployed at other |
| | 46 | sites. Our strategy is push for early adoption of the federation software, |
| | 47 | before it is fully complete, so that its development can be guided by lessons |
| | 48 | learned during deployment. |
| | 49 | |
| | 50 | We participated in GEC3, giving a talk and a demo, and had discussions with |
| | 51 | several other projects while there. We also attended the GENI-FIRE meeting in |
| | 52 | Madrid, giving a talk and having discussions with possible international |
| | 53 | collaborators. |
| | 54 | |
| | 55 | === B. Project participants === |
| | 56 | |
| | 57 | University of Utah |
| | 58 | |
| | 59 | Subcontracts for HP and Internet2 are pending, as Utah's contract with BBN was executed only in December. |
| | 60 | |
| | 61 | === C. Publications (individual and organizational) === |
| | 62 | |
| | 63 | We presented a poster at OSDI 2008, accompanied by a demo (the same one given at GEC #3). Poster and demo were well-received. |
| | 64 | |
| | 65 | Title: ProtoGENI: A Network for Next-Generation Internet Research |
| | 66 | |
| | 67 | Authors: Robert Ricci, Jay Lepreau, Leigh Stoller, Mike Hibler, and David Johnson |
| | 68 | |
| | 69 | === D. Outreach activities === |
| | 70 | |
| | 71 | Our poster and demo at OSDI gave us an opportunity to discuss GENI with a number of people involved in the distributed systems community, many of which weren't yet familiar with GENI, or who had questions regarding it. We also participated in the GPO's outreach activity to the European community in Madrid. |
| | 72 | |
| | 73 | === E. Collaborations === |
| | 74 | |
| | 75 | Beginning in early October, we have organized bi-weekly conference calls with |
| | 76 | the members of our cluster, in order to foster collaboration within it. |
| | 77 | Participants have included all groups initially assigned to our cluster, our |
| | 78 | subcontractors, the Programmable Edge Node project, and the Security |
| | 79 | Architecture project. |
| | 80 | |
| | 81 | We have interacted with a number of other GPO-funded projects within and |
| | 82 | outside of our cluster about collaborations and integrations, including: |
| | 83 | |
| | 84 | BGP Mux: Held a discussion with this group and others about how the virtualization work they are doing can be used by our project and connected to the Programmable Edge Node project. We are in the process of looking at the implementation they have thus far. Georgia Tech also now hosts two ProtoGENI edge nodes. |
| | 85 | |
| | 86 | CMU Testbeds: Providing code/software support to this project as they come up to speed on the Emulab and ProtoGENI software for deployment of !HomeNet. |
| | 87 | |
| | 88 | Instrumentation Tools: They have given a demo of their existing work to one of our cluster conference calls, and we have begun talks about the specific tasks needed to integrate their work into ProtoGENI. The University of Kentucky will soon host two ProtoGENI edge nodes. |
| | 89 | |
| | 90 | Measurement System: Have had discussions about the specifics of how integration with this project will work, and running the necessary Emulab code to join our clearinghouse. Also discussed possible low-layer connectivity between our projects. The University of Wisconsin-Madison now hosts two ProtoGENI edge nodes. |
| | 91 | |
| | 92 | Enterprise GENI: Exploring the idea of providing !OpenFlow capabilities on the ProtoGENI backbone |
| | 93 | |
| | 94 | SPP Overlay Nodes: Considering sharing the bandwidth provided by Internet2 with this project, using the switches to be purchased under our contract. We have also had discussions with the GPO and Internet2 regarding this arrangement. |
| | 95 | |
| | 96 | Million-Node GENI: Working on making this project available in a controlled environment, and running it on ProtoGENI nodes. |
| | 97 | |
| | 98 | Programmable Edge Node: This project has joined our cluster, and we have had talks about how integrate this project with the work that we and others in our cluster are doing. |
| | 99 | |
| | 100 | GMOC: Initial talks about providing emergency shutdown and operational information |
| | 101 | |
| | 102 | Security Architecture: This project has been a regular participant in our cluster conference calls. |
| | 103 | |
| | 104 | DETER: Initial contact regarding the Deter Federation Daemon, and possible low-layer interconnect between the clusters |
| | 105 | |
| | 106 | PlanetLab: We have been in occasional contact with this project, with the goal of reducing the differences between the APIs provided by these two control frameworks |
| | 107 | |
| | 108 | We have also been in close contact with the GPO, including a demo of Emulab and |
| | 109 | ProtoGENI to the GPO technical staff. We responded to the Substrate Working |
| | 110 | Group's call for information regarding hardware to be deployed, and also posted |
| | 111 | this information on protogeni.net . We have been working with Internet2 and |
| | 112 | our campus OIT to plan the backbone to de deployed under this subcontract. We |
| | 113 | have been in close contact with our other subcontractor, HP, regarding their |
| | 114 | role of providing switches and hosting an edge cluster, and they will soon host |
| | 115 | two ProtoGENI edge nodes. Finally, we have held preliminary discussions with |
| | 116 | international Emulab sites about possible international federation efforts. |
| | 117 | |
| | 118 | === F. Other Contributions === |
| | 119 | |
