ENTGENI and OFSTAN Spiral 2 Year-end Project Review

ENTGENI and OFSTAN Spiral 2 Year-end Project Review Stanford University PI: Staff: Students: Nick Mc. Keown, Guru Parulkar Guido Appenzeller, Masayoshi Kobayashi, Johan van Reijendam, Srini Seetharaman, Rob Sherwood, Dan Talayco, Paul Weissmann, Tatsuya Yabe David Erickson, Glen Gibb, Jad Naous, KK Yap, Yiannis Yiakoumis Aug-25 -2010 Sponsored by the National Science Foundation 1

Goal Build and deploy Open. Flow networking substrate for GENI • Sliceable and programmable • Support research and production use on same substrate • Integrated with GENI control framework Sponsored by the National Science Foundation 25 -Aug-2010

Scope • Revise and maintain Open. Flow spec & reference implementations • Design, build, and maintain software components – Flow. Visor, Expedient, SNAC, NOX and a set of tools • Deploy Open. Flow in Stanford campus – Mc. Keown group production network and open wireless (ofwifi) • Support other campus deployments – Production and research use as part of GENI – Build larger Open. Flow community • Integrate with GENI – With control framework and computing substrate • Create compelling demonstrations – With other campuses Sponsored by the National Science Foundation 25 -Aug-2010

Accomplishments • Released Open. Flow 1. 0 and working on Open. Flow 1. 1 – GEC 9 to use Open. Flow 1. 0 that is starting to be relatively stable – Supports slicing for isolation among experiments • New release for all major software components: FV, NOX, Expedient – Support OF 1. 0 – Expedient as OF aggregate manager supports GENI API and Opt-in – Expedient as a “plug and play” clearinghouse – demonstrated at GEC 8 • Stanford deployment – Expanded to include more production and experiment users – Expanded to use OF switches from more vendors • Campus deployments – All of them have OF deployments and getting ready for GEC 9 – Used for both limited production and research use Sponsored by the National Science Foundation 25 -Aug-2010

Accomplishments (contd. ) • GENI Integration – A preliminary integration demo at GEC 8: featured various components on computing and networking substrates at GPO and Stanford – Some progress on an end to end Open. Flow network: control plane and data plane interconnection being worked on • Building a larger community – Talks, CIO summit, documentation, HOWTO guides, tutorials, mailing lists – Preliminary survey: OF deployments in 68 institutions spanning 13 countries • Built strong collaboration between Stanford and GPO – With both Heidi’s team and Tom’s team – Opportunity to build on it further for GEC 9 and long term GENI Sponsored by the National Science Foundation 25 -Aug-2010

Support Overview Level 1 Level 2 Level 3 NOX: Stanford and Berkeley Flow. Visor: Stanford Expedient/Opt-In: Stanford Indigo: Big Switch Networks Switches General Open. Flow Support: Stanford Local Campus IT SNAC: Big Switch Networks HP: HP Support NEC: NEC Support. . . Support has been through bi-weekly calls, tutorials, online guides, mailing lists, bug tracking, and onsite visits Sponsored by the National Science Foundation 23

Connectivity Update • GPO and Stanford collaborating in providing end-to-end Layer-2 connectivity to experimenters • Inter-connectivity of campuses proceeding on target – NLR connectivity status 3700 Univ Wisconsin Madison (complete) 3702 Indiana Univ (in progress) 3704 BBN (complete) 3705 Shared monitoring and testing (complete) 3707 Clemson (complete) 3709 Georgia Tech (complete) 3715 NLR-Open. Flow-Core (South) (in progress) 3716 NLR-Open. Flow-Core (North) (in progress) – Washington, Rutgers and Princeton connecting through Net. FPGA Open. Flow switches in Internet 2 Sponsored by the National Science Foundation 25 -Aug-2010

GENI Integration Update • Demonstrated successful control-plane integration of Open. Flow substrate with computing substrates using common GENI API – The Open. Flow aggregate manager was upgraded to support the GENI API. We dynamically created slices using it Sponsored by the National Science Foundation 25 -Aug-2010

Milestone & QSR Status: ENTGENI ID Milestone Status On Time? S 2. a Release Open. Flow 1. 0. Delivered on Dec 31, 2009 Yes S 2. b Support Campus Installation of Open. Flow 1. 0 Delivered. Ga. Tech/Clemson transitioned in Aug 2010, all others transitioned by GEC 8 Yes S 2. c Upgrade and maintain Flow. Visor, Aggregate Manager and deployment tools. Delivered. New Flow. Visor is running on all campuses. Expedient is publicly available and undergoing deployment Yes S 2. d Integrate Open. Flow, Planet. Lab Control Delivered. This was demonstrated Framework (SFI), GENI API, and NOX on in GEC 8. Stanford campus (primary responsibility is with Princeton and GPO. Yes S 2. e Integration testing with Planet. Lab, I 2, NLR, and GPO for end-to-end Open. Flow dataplane and Openflow/AM/SFI control plane. Delivered. This was demonstrated in GEC 8 Yes S 2. f Coordinate campus support interface with Nicira. Yes S 2. g Coordinate development support for improved NOX packaging, documentation and usability with developers at ICSI and Nicira. Actively supporting or coordinating these activities (These are always ongoing and do not have a finite end) S 2. h Support I 2 and NLR Open. Flow system design, deployment and debugging. Sponsored by the National Science Foundation 25 -Aug-2010 On Wiki? GPO signoff?

Milestone & QSR Status: OFSTAN ID Milestone Status On Time? S 2. a Continue to build E-GENI at Stanford Our deployment transitioned to 1. 0 and has expanded (in the past 1 year) to 25 wired users and 25 wireless users. Support use of E-GENI at Stanford by other GENI researchers -- very limited number of pre-approved users -- most likely users participating in the demo. Stanford E-GENI networks (experimental and demo network) were opened up for several researchers to conduct demos Yes S 2. c Provide training and documentation for E-GENI Extensive documentation to deploy Open. Flow (foswiki), develop Open. Flow experiments (NOX doxygen, and Open. Flow tutorial in GEC 8) GPO signoff? Yes S 2. b On Wiki? Yes Sponsored by the National Science Foundation 25 -Aug-2010 31

Milestone & QSR Status: OFNOX ID Milestone Status On Time? S 2. a Publish NOX feature list Delivered. Release NOX supporting Open. Flow 1. 0 Delivered. Openflow-1. 0 branch Yes S 2. c Initial rough NOX API documentation Delivered. Using doxygen Yes S 2. d Release software that supports Open. Flow 1. 0 configuration protocol, and NOX API V 2 Delivered. Openflow-1. 0 branch Yes S 2. e Support campus installations of GENI software with AM API Ongoing (no finite end) Yes S 2. f Port existing applications to latest Open. Flow identifiers Delivered. Released transition notes Yes and work with individual teams to port their apps S 2. g Add support for multiple Openflow protocols Not planned for S 2. h Increase portability Delivered. Published guide for porting Yes to Cent. OS and reduced dependency S 2. i Release 1 st ver SNAC/NOX console software Delivered. Also in NOX-destiny. Yes S 2. j Plan and engineer GEC 9 demo Ongoing Yes S 2. k Support campuse upgrades to OF 1. 0 and GENI API Delivered. All campuses transitioned Yes S 2. l Improve system and regression test support Ongoing Yes S 2. m Publish feature list for 2011 releases Ongoing GPO signoff? No S 2. b On Wiki? Yes Sponsored by the National Science Foundation 25 -Aug-2010 - 32

Program Changes • Nicira deciding to drop off • – Implications on NOX and SNAC – Realization that NOX belongs in the university Unavoidable slow down. End result likely to be better. Toroki not working out as a provider of inexpensive OF switches • Big. Switch stepping up – To continue to develop and support SNAC – To continue to develop and support Indigo reference implementation More central to its business and so we can expect good results • ICSI/Berkeley and Stanford are stepping up – To continue to develop and support NOX – To Build an open source community around it Good for the research community • Expedient – A significant new activity – Decided not to do just a simple aggregate manager Sponsored by the National Science Foundation 25 -Aug-2010

Issues • GENI Integration: Not as mature as we would like – GPO and Stanford collaboration for GEC 8 provided good start – Proposed plan between GPO and Stanford encouraging • Software release and support – Need more fine tuning and consensus building • Internet 2 moving slowly – Can be an issue • Inter-campus connectivity harder than we thought – Requiring coordination by many parties and lot of logistics – Have to keep pushing and get it all working soon Sponsored by the National Science Foundation 25 -Aug-2010

GENI Integration Plans • Expedient and Opt-in Manager testing and deployment – By Aug 30, perform necessary internal testing of Open. Flow control stack and tag working version – Track bugs and generate regression tests for bugs discovered • Proposed plan between BBN and Stanford – BBN and Stanford will in parallel do following tests: • install FV/Expedient/Opt. In Manager • use this stack to reserve an Openflow slice • ensure candidate demos run – By Sept 15, generate RPMs/DEBs that have been tested and produce necessary documentation for campuses to rollout Sponsored by the National Science Foundation 25 -Aug-2010

GEC 9 Demo Support • Main activities – Allow each campus to operate their own Aggregate manager and Opt-in manager – Verify control plane integration – Verify data plane integration • Connect demo networks in each campus to NLR/Internet 2 – Perform dry-runs and testing for GEC 9 – Polish demos • Tech support for other campuses – Help transition software to latest supported version Sponsored by the National Science Foundation 25 -Aug-2010

Post-GEC 9 Plans • Scale up the production network to include more users • The GPO is starting to formulate goals for Spiral 3. What are your thoughts regarding potential Spiral 3 work? – – – – Streamline campus support Scale OF deployments on campuses for research and production use Get more campuses ready for OF deployments More involvement of the core networks and regional networks Increased scale of experiments Ensure safe resource allocation across experiments Provide OF network and GENI racks integration Sponsored by the National Science Foundation 25 -Aug-2010

Final Takeaways • We are on track to build and deploy Open. Flow networking substrate for GENI – Different components and deployments coming together – Very good collaboration with campuses and GPO • We are excited about and focused on GEC 9 Two issues – Open. Flow and GENI control framework integration – Inter-campus connectivity Both seem to be under control with a plan – we need to execute • Exciting long term prospects – For scaling Open. Flow networks on campuses – For Open. Flow and software defined networking in general Sponsored by the National Science Foundation 25 -Aug-2010