| | 1 | [[PageOutline]] |
| | 2 | |
| | 3 | = OFCLEM Project Status Report = |
| | 4 | |
| | 5 | Period: 4Q09 |
| | 6 | == I. Major accomplishments == |
| | 7 | The project contract is fully executed on 11/30/09. The project will deploy an !OpenFlow testbed on |
| | 8 | the Clemson University campus and connect with wireless mesh access points and mobile |
| | 9 | terminals. This trial will conduct !OpenFlow experimentation focused on !OpenFlow enabled |
| | 10 | network operation solutions as a precursor to deployment into Clemson research and production |
| | 11 | networks. |
| | 12 | During this period, key achievements include: |
| | 13 | a. Project kickoff meeting at GEC6 (11/16-18, 2009). |
| | 14 | a. Confirmed GEC7 demo plan. |
| | 15 | a. Acquired one Toroki !OpenFlow switch. |
| | 16 | a. Began installation of NOX, !FlowVisor, !OpenFlow controllers, PC Engine !OpenFlow implementation, and !PlanetLab. |
| | 17 | |
| | 18 | === A. Milestones achieved === |
| | 19 | The only one planned milestone for this reporting period is to select !OpenFlow switch vendors |
| | 20 | before 12/31/09.[[BR]] |
| | 21 | |
| | 22 | We have acquired one Toroki switch. We have been communicating with Juniper extensively |
| | 23 | during this period to urge it to support !OpenFlow. According to Juniper, it currently does not |
| | 24 | support !OpenFlow, but only make its SDK compatible for customers to integrate their own |
| | 25 | !OpenFlow implementation. With Stanford, we continue to approach Juniper urging its support for |
| | 26 | !OpenFlow v1.0. |
| | 27 | |
| | 28 | === B. Deliverables made === |
| | 29 | a. GEC7 demo plan |
| | 30 | |
| | 31 | == II. Description of work performed during last quarter == |
| | 32 | |
| | 33 | === A. Activities and findings === |
| | 34 | a. GEC7 demo plan (Mar. 2010) |
| | 35 | The GEC7 Clemson demo will consist of the following components: |
| | 36 | 1. Minimum 3-switch configuration: One Toroki switch + two PC engines AP. |
| | 37 | 1. !OpenFlow VLAN + 1 non-!OpenFlow VLAN serving servers/laptops in our lab. |
| | 38 | 1. Nicira NOX, !FlowVisor, Nicira !OpenFlow controller with Net Admin Console |
| | 39 | 1. Optional functionality: Stanford !OpenRoads controller, mesh network handoff/routing on PC engines AP.[[BR]] |
| | 40 | The base demo will show the proper functioning of the 3-switch network. The optional components are dependent on working progress and will be shown if available. |
| | 41 | b . Switch acquisition |
| | 42 | The Clemson project has two missions – campus network integration and wireless mesh network for mobile access. For campus integration, we proposed to create a test network closely mirroring Clemson’s production network (currently based on Cisco and Juniper switches). To produce convincing results for our production network integration, it is our IT’s request that the test be conducted with our same Cisco and Juniper switches. |
| | 43 | |
| | 44 | '''!OpenFlow Campus Trials at Clemson University (1833A)'''[[BR]] |
| | 45 | In this last quarter, we have communicated extensively with Cisco and Juniper regarding |
| | 46 | their !OpenFlow releases. So far Cisco and Juniper switches are not !OpenFlow-ready for our trials. [[BR]] |
| | 47 | As a low cost ($4,500) and immediately available option, we acquired one Toroki switch (90-day evaluation, 11/30/09-03/01/10; official purchase will be in Jan/Feb 2010 if integration is successful) to begin our trial configuration. The unit has arrived and is currently being configured. |
| | 48 | === B. Project participants === |
| | 49 | The project team members are: |
| | 50 | PI: Kuang-Ching Wang [[BR]] |
| | 51 | ECE graduate research assistants: Sajindra Pradhananga (MS), Glenn Evans (MS)[[BR]] |
| | 52 | ECE undergraduate students: Bradley Collins (senior), Aaron Rosen (senior)[[BR]] |
| | 53 | === C. Publications (individual and organizational) === |
| | 54 | Not available at this time. |
| | 55 | |
| | 56 | === D. Outreach activities === |
| | 57 | An announcement has been made to recruit two South Carolina high school students to |
| | 58 | participate in a 6-week summer internship program with this project group. |
| | 59 | |
| | 60 | === E. Collaborations === |
| | 61 | The project is conducted in collaboration with campuses and backbone providers on the !OpenFlow |
| | 62 | trial. We have so far worked more closely with: |
| | 63 | Nick !McKeown, Guru Parulkar, Guido Appenzeller and the Stanford !OpenFlow group, assisting us in the acquisition, installation, configuration, and testing of !OpenFlow software. |
| | 64 | === F. Other Contributions === |
| | 65 | Not available at this time. |
