170 likes | 322 Views
ENTGENI and OFSTAN Spiral 2 Year-end Project Review. Stanford University PI: Nick McKeown, Guru Parulkar Staff: Guido Appenzeller, Masayoshi Kobayashi, Johan van Reijendam, Srini Seetharaman, Rob Sherwood, Dan Talayco, Paul Weissmann, Tatsuya Yabe
E N D
ENTGENI and OFSTANSpiral 2 Year-end Project Review Stanford University PI: Nick McKeown, Guru Parulkar Staff: Guido Appenzeller, Masayoshi Kobayashi, Johan van Reijendam, Srini Seetharaman, Rob Sherwood, Dan Talayco, Paul Weissmann, Tatsuya Yabe Students: David Erickson, Glen Gibb, Jad Naous, KK Yap, Yiannis Yiakoumis Aug-25-2010
Goal Build and deploy OpenFlow networking substrate for GENI • Sliceable and programmable • Support research and production use on same substrate • Integrated with GENI control framework 25-Aug-2010
Scope • Revise and maintain OpenFlow spec & reference implementations • Design, build, and maintain software components • FlowVisor, Expedient, SNAC, NOX and a set of tools • Deploy OpenFlow in Stanford campus • McKeown group production network and open wireless (ofwifi) • Support other campus deployments • Production and research use as part of GENI • Build larger OpenFlow community • Integrate with GENI • With control framework and computing substrate • Create compelling demonstrations • With other campuses 25-Aug-2010
Accomplishments • Released OpenFlow 1.0 and working on OpenFlow 1.1 • GEC9 to use OpenFlow 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 OF1.0 • Expedient as OF aggregate manager supports GENI API and Opt-in • Expedient as a “plug and play” clearinghouse – demonstrated at GEC8 • 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 GEC9 • Used for both limited production and research use 25-Aug-2010
Accomplishments (contd.) • GENI Integration • A preliminary integration demo at GEC8: featured various components on computing and networking substrates at GPO and Stanford • Some progress on an end to end OpenFlow 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 GEC9 and long term GENI 25-Aug-2010
Support Overview Level 1 Level 2 Level 3 Local Campus IT General OpenFlow Support: Stanford SNAC: Big Switch Networks NOX: Stanford and Berkeley FlowVisor: Stanford Expedient/Opt-In: Stanford Indigo: Big Switch Networks HP: HP Support Switches NEC: NEC Support ... Support has been through bi-weekly calls, tutorials, online guides, mailing lists, bug tracking, and onsite visits
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-OpenFlow-Core (South) (in progress) 3716 NLR-OpenFlow-Core (North) (in progress) Washington, Rutgers and Princeton connecting through NetFPGA OpenFlow switches in Internet2 Connectivity Update 25-Aug-2010
Demonstrated successful control-plane integration of OpenFlow substrate with computing substrates using common GENI API The OpenFlow aggregate manager was upgraded to support the GENI API. We dynamically created slices using it GENI Integration Update 25-Aug-2010
Milestone & QSR Status: ENTGENI 25-Aug-2010
Milestone & QSR Status: OFSTAN 25-Aug-2010
Milestone & QSR Status: OFNOX 25-Aug-2010
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 • BigSwitch 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 25-Aug-2010
Issues • GENI Integration: Not as mature as we would like • GPO and Stanford collaboration for GEC8 provided good start • Proposed plan between GPO and Stanford encouraging • Software release and support • Need more fine tuning and consensus building • Internet2 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 25-Aug-2010
GENI Integration Plans • Expedient and Opt-in Manager testing and deployment • By Aug 30, perform necessary internal testing of OpenFlow 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/OptIn 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 25-Aug-2010
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/Internet2 Perform dry-runs and testing for GEC9 Polish demos Tech support for other campuses Help transition software to latest supported version GEC9 Demo Support 25-Aug-2010
Post-GEC9 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 25-Aug-2010
Final Takeaways • We are on track to build and deploy OpenFlow networking substrate for GENI • Different components and deployments coming together • Very good collaboration with campuses and GPO • We are excited about and focused on GEC9Two issues • OpenFlow 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 OpenFlow networks on campuses • For OpenFlow and software defined networking in general 25-Aug-2010