| | 1 | = DTunnels Quarterly Status Report for 4Q 2008 = |
| | 2 | |
| | 3 | == I. Major accomplishments == |
| | 4 | |
| | 5 | === A. Milestones achieved === |
| | 6 | |
| | 7 | * BGPMux control plane configuration and README file |
| | 8 | |
| | 9 | The BGP Mux control plane configuration has been successfully tested and deployed on two VINI nodes with upstream connectivity from PSG Net. |
| | 10 | |
| | 11 | The GENI Trac Web site has a bare-bones README file describing the setup. We are in the process of augmenting this setup to support data plane connectivity to downstream client networks. |
| | 12 | |
| | 13 | === B. Deliverables made === |
| | 14 | |
| | 15 | * BGPMux initial configuration and README. |
| | 16 | |
| | 17 | We have deployed a version of the BGP Mux on two VINI nodes and integrated the BGPMux with upstream connectivity from Verio and Sprint on the VINI testbed. |
| | 18 | |
| | 19 | We have published a README describing the setup. This README is a working document which we will update with more details as we continue to develop the BGPMux. |
| | 20 | |
| | 21 | == II. Description of work performed during the last quarter == |
| | 22 | |
| | 23 | === A. Activities and Findings === |
| | 24 | |
| | 25 | * BGPMux Development |
| | 26 | |
| | 27 | In addition to the deployment of the BGP Mux on the VINI testbed, we have been working with the ProtoGENI group to deploy the BGPMux on the ProtoGENI nodes. |
| | 28 | |
| | 29 | * Upstream Connectivity for BGP Mux |
| | 30 | |
| | 31 | We have not received any confirmation from the GPO or from other groups that the ProtoGENI nodes will have upstream connectivity or IPv4 prefixes to announce from the ProtoGENI testbed. |
| | 32 | |
| | 33 | * Tunnels Development |
| | 34 | |
| | 35 | We have begun investigating libvirt as a mechanism for creating virtual networks (nodes and links), as a possible interface to the protoGENI clearinhouse/control framework. |
| | 36 | |
| | 37 | We have an initial setup whereby a controller can create virtual nodes and links via the libvirt interface in an OpenVZ environment. The next step will involve creation of virtual links with tunnels via the libvirt interface, and meeting with the ProtoGENI group to ensure that their control framework will support this interface. |
| | 38 | |
| | 39 | === B. Publications (individual and organizational) === |
| | 40 | |
| | 41 | None this quarter. |
| | 42 | |
| | 43 | === C. Outreach activities === |
| | 44 | |
| | 45 | None this quarter. |
| | 46 | |
| | 47 | === D. Collaborations === |
| | 48 | |
| | 49 | ProtoGENI: Held a discussion with this group about how the libvirt interface can be integrated with the ProtoGENI control framework. We have not yet finalized any design/interfaces. We are also hosting two ProtoGENI nodes at Georgia Tech. |
| | 50 | |
| | 51 | === E. Other Contributions === |
| | 52 | |
