| 1 | = ProtoGENI Project Status Report = |
| 2 | |
| 3 | Period: 1Q 2009 |
| 4 | |
| 5 | == I. Major accomplishments == |
| 6 | |
| 7 | === A. Milestones achieved === |
| 8 | |
| 9 | '''Year 1(c): Basic clearinghouse and aggregate manager up and running''' |
| 10 | |
| 11 | We have released our clearinghouse software under the GENI Public License. The clearinghouse has two main roles: |
| 12 | * To act as a central trust anchor for federates |
| 13 | * To provide a set of registries for component managers, slice authorities, slices, and users, so that these entities can find one another |
| 14 | |
| 15 | More details of the capabilities, including complete API documentation, can be found here: http://www.protogeni.net/trac/protogeni/wiki/ClearingHouseDesc. [[BR]] |
| 16 | The installation documentation here can be found here: http://www.protogeni.net/trac/protogeni/wiki/InstallingAClearingHouse |
| 17 | |
| 18 | An aggregate manager based on the Emulab software is now running at 4 sites: Utah, Kentucky, Wisconsin, and CMU. This AM is capable of: |
| 19 | * Provisioning "raw" PCs and PlanetLab slivers |
| 20 | * Creating VLANs within a single aggregate |
| 21 | * Creating IP-in-IP tunnels between different aggregates |
| 22 | * Support for our RSpec format for resource advertisement and sliver descriptions (ticket requests) |
| 23 | * Federation through a shared clearinghouse |
| 24 | |
| 25 | This aggregate manager is part of the Emulab codebase, and is implemented as a new API to Emulab resource manipulation. It is available under the AGPLv3 directly from Emulab CVS. |
| 26 | |
| 27 | More details on the capabilities of this AM can be found at: http://www.protogeni.net/trac/protogeni/wiki/AggregateManager [[BR]] |
| 28 | API documentation is here: http://www.protogeni.net/trac/protogeni/wiki/ComponentManagerAPI [[BR]] |
| 29 | Instructions for enabling the AM APIs on an Emulab installation are here: https://www.protogeni.net/trac/protogeni/wiki/ProtoGENIInstall |
| 30 | |
| 31 | '''Year 1(g): Gave demos of progress at GEC #3 and GEC #4''' |
| 32 | |
| 33 | We demonstrated the abilities of the clearinghouse and aggregate manager listed above at GEC #3 and GEC #4, plus: |
| 34 | * A proof-of-concept GUI for describing GENI slices, including topology specification |
| 35 | * A working federation of 4 sites |
| 36 | * Emergency shutdown of slices |
| 37 | * Delegation of credentials |
| 38 | |
| 39 | Poster from the GEC3, which included material from the demo: http://www.protogeni.net/trac/protogeni/wiki/GEC3Poster |
| 40 | Poster used in the presentation of the GEC4 demo: http://www.protogeni.net/trac/protogeni/wiki/GEC4Poster |
| 41 | |
| 42 | We also made significant progress on "control plane integration of cluster |
| 43 | partners" milestone, more details can be found below. |
| 44 | |
| 45 | === B. Deliverables made === |
| 46 | |
| 47 | Release of clearinghouse software under the GENI Public License Documentation here: http://www.protogeni.net/trac/protogeni/wiki/InstallingAClearingHouse |
| 48 | |
| 49 | Significant progress on our RSpec prototype was released publicly at: http://www.protogeni.net/trac/protogeni/wiki/RSpec |
| 50 | |
| 51 | Improvements include: |
| 52 | * Changes to support the needs of the !HomeNet project |
| 53 | * Support for annotations mapping requested links to specific physical paths |
| 54 | * Re-working of the identifiers used to identify and bind resources |
| 55 | |
| 56 | Ongoing (listed in last report, still going strong): |
| 57 | Documentation of design decisions and plans up at http://www.protogeni.net/ [[BR]] |
| 58 | Early credential and ticket formats (still in progress) released at: http://www.protogeni.net/trac/protogeni/wiki/Authentication |
| 59 | |
| 60 | == II. Description of work performed during last quarter == |
| 61 | |
| 62 | === A. Activities and findings === |
| 63 | |
| 64 | As before, much of the activity billable this quarter to this contract has been |
| 65 | integration and collaboration (see below). |
| 66 | |
| 67 | The most significant progress we have made this quarter is the running of a |
| 68 | federation, which joins together four of the projects in our cluster: Utah, |
| 69 | Kentucky, Wisconsin, and CMU. This is a full control-plane federation, in which |
| 70 | all members act as independent Slice Authorities and Component Managers, |
| 71 | establishing trust through a shared Clearinghouse (run at Utah). The APIs and |
| 72 | data structures used to communicate among the federates, and for users to access |
| 73 | the federates, are our versions of the GENI APIs. All federates at this time |
| 74 | are running versions of the Emulab software. |
| 75 | |
| 76 | Users may request slices that include network topologies - links within a |
| 77 | federate are realized as VLANs, and links between federates are currently |
| 78 | realized as IP-in-IP tunnels. When the backbone is built out, it will be a |
| 79 | member of this federation, and will enable end-to-end VLAN connectivity between |
| 80 | a few of the federates (pending the assistance of regional and campus networks). |
| 81 | |
| 82 | Documentation for joining the federation is here: http://www.protogeni.net/trac/protogeni/wiki/BecomingAProtoGENISite |
| 83 | |
| 84 | API documentation is here: |
| 85 | http://www.protogeni.net/trac/protogeni/wiki/ClearingHouseDesc [[BR]] |
| 86 | http://www.protogeni.net/trac/protogeni/wiki/SliceAuthorityAPI [[BR]] |
| 87 | http://www.protogeni.net/trac/protogeni/wiki/ComponentManagerAPI [[BR]] |
| 88 | |
| 89 | A set of scripts to use these APIs are described here: http://www.protogeni.net/trac/protogeni/wiki/TestScripts |
| 90 | |
| 91 | Under other funding, we have made progress on a number of other important |
| 92 | tasks, including: |
| 93 | Support for delegation of credentials, which includes a further fleshing out of our security model. Described at: http://www.protogeni.net/trac/protogeni/wiki/DelegationExample [[BR]] |
| 94 | Progress on a slice embedding service, by adding support for RSpec to Emulab's "assign" (resource mapper)[[BR]] |
| 95 | Support for simple emergency shutdown of slices[[BR]] |
| 96 | Very early support for OpenVZ-based slicing inside of the Emulab testbed |
| 97 | |
| 98 | We were heavily involved in GEC4, giving three talks, a demo, a poster, and running 6 hours of cluster meeting time. We have also been involved in the |
| 99 | planning for GEC6, to be held in Salt Lake City. |
| 100 | |
| 101 | === B. Project participants === |
| 102 | |
| 103 | University of Utah |
| 104 | |
| 105 | Subcontracts for HP and Internet2 still under negotiation, due to uncertainties about which Internet2 sites to use in first year - proceeding now that those have been decided |
| 106 | |
| 107 | === C. Publications (individual and organizational) === |
| 108 | |
| 109 | === D. Outreach activities === |
| 110 | |
| 111 | As part of Solicitation 2, we had discussions with a large number of |
| 112 | institutions that are not already part of GENI, encouraging more participation. |
| 113 | This included a number of international collaborators. |
| 114 | |
| 115 | We addressed a meeting of the QUILT, a group of regional networks (primarily |
| 116 | academic), about how they can get involved in GENI. |
| 117 | |
| 118 | === E. Collaborations === |
| 119 | |
| 120 | We have continued to organize bi-weekly Cluster C conference calls, which |
| 121 | have helped our cluster members to make progress together. In addition to |
| 122 | the members assigned to our cluster, the Security Architecture project has been |
| 123 | a frequent participant, and some calls have featured members of th GPO and |
| 124 | other invited projects. |
| 125 | |
| 126 | The following projects have integrated with our clearinghouse by joining our |
| 127 | federation (described above): |
| 128 | CMU Testbeds[[BR]] |
| 129 | Instrumentation Tools[[BR]] |
| 130 | Measurement System |
| 131 | |
| 132 | The following project has added support for its substrate to the Emulab |
| 133 | software, bringing it very close to clearinghouse integration: |
| 134 | Programmable Edge node |
| 135 | |
| 136 | We have begun working out RSpec compatibility with the following project: |
| 137 | DTunnels/BGP Mux |
| 138 | |
| 139 | We have also interacted with a number of other GPO-funded projects outside of |
| 140 | our cluster, including: |
| 141 | |
| 142 | SPP Overlay Nodes: Cooperating to share Internet2 donated wave, have been working out details of when, where, and how equipment will be placed at shared POPs |
| 143 | GMOC: Currently evaluating a proposal by the GMOC for using URNs to identify users and resources in GENI. Have also discussed the set of operational data we can collect |
| 144 | Security Architecture: In continuous contact to refine our security model |
| 145 | Million-Node GENI: Now available on Emulab testbed, and plan to soon add support for automatically giving ProtoGENI users "Seattle" accounts |
| 146 | Mid-Atlantic Network: Have had a discussion about the capabilities of DRAGON and how it could be useful to ProtoGENI in the medium (but probably not short) term |
| 147 | Great Plains Network: Have given them an account on Emulab so that they can see how our control framework is put together |
| 148 | |
| 149 | We participated in a GPO-sponsored meeting held in Denver in February, |
| 150 | primarily composed of Cluster B members, to work out issues relating to the |
| 151 | role of the clearinghouse in interacting with aggregate managers. |
| 152 | |
| 153 | We have continued to be heavily involved in the Control Framework and Services |
| 154 | working groups, through in-person meetings, conference calls, and email |
| 155 | discussions. |
| 156 | |
| 157 | === F. Other Contributions === |