Sponsored by the National Science Foundation 1
ENTGENI and OFSTANSpiral 2 Year-end Project Review
Stanford University
PI: Nick McKeown, Guru ParulkarStaff: 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
Sponsored by the National Science Foundation 2
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
Sponsored by the National Science Foundation 3
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
Sponsored by the National Science Foundation 4
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
Sponsored by the National Science Foundation 5
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
Sponsored by the National Science Foundation 23
Support Overview
SNAC: Big Switch NetworksSNAC: Big Switch Networks
NOX: Stanford and BerkeleyNOX: Stanford and Berkeley
FlowVisor: StanfordFlowVisor: Stanford
Switc
hes
Switc
hes
Expedient/Opt-In: StanfordExpedient/Opt-In: Stanford
Indigo: Big Switch NetworksIndigo: Big Switch Networks
HP: HP SupportHP: HP Support
NEC: NEC SupportNEC: NEC Support
......
Level 1 Level 2 Level 3
Support has been through bi-weekly calls, tutorials, online guides, mailing lists, bug tracking, and onsite visits
Sponsored by the National Science Foundation 24
Connectivity Update
25-Aug-2010
• 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
Sponsored by the National Science Foundation 26
GENI Integration Update
• 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
25-Aug-2010
Sponsored by the National Science Foundation 30
Milestone & QSR Status: ENTGENI
ID Milestone Status On Time?
On Wiki?
GPO signoff?
S2.a Release OpenFlow 1.0. Delivered on Dec 31, 2009 Yes
S2.b Support Campus Installation of OpenFlow 1.0 Delivered. GaTech/Clemson transitioned in Aug 2010, all others transitioned by GEC8
Yes
S2.c Upgrade and maintain FlowVisor, Aggregate Manager and deployment tools.
Delivered. New FlowVisor is running on all campuses. Expedient is publicly available and undergoing deployment
Yes
S2.d Integrate OpenFlow, PlanetLab Control Framework (SFI), GENI API, and NOX on Stanford campus (primary responsibility is with Princeton and GPO.
Delivered. This was demonstrated in GEC8.
Yes
S2.e Integration testing with PlanetLab, I2, NLR, and GPO for end-to-end OpenFlow dataplane and Openflow/AM/SFI control plane.
Delivered. This was demonstrated in GEC8
Yes
S2.f Coordinate campus support interface with Nicira.
Actively supporting or coordinating these activities (These are always ongoing and do not have a finite end)
Yes
S2.g Coordinate development support for improved NOX packaging, documentation and usability with developers at ICSI and Nicira.
S2.h Support I2 and NLR OpenFlow system design, deployment and debugging.
25-Aug-2010
Sponsored by the National Science Foundation 31
Milestone & QSR Status: OFSTAN
ID Milestone Status On Time?
On Wiki?
GPO signoff?
S2.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.
Yes
S2.b 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
S2.c Provide training and documentation for E-GENI
Extensive documentation to deploy OpenFlow (foswiki), develop OpenFlow experiments (NOX doxygen, and OpenFlow tutorial in GEC8)
Yes
25-Aug-2010
Sponsored by the National Science Foundation 32
Milestone & QSR Status: OFNOX
ID Milestone Status On Time?
On Wiki?
GPO signoff?
S2.a Publish NOX feature list Delivered. No
S2.b Release NOX supporting OpenFlow 1.0 Delivered. Openflow-1.0 branch Yes
S2.c Initial rough NOX API documentation Delivered. Using doxygen Yes
S2.d Release software that supports OpenFlow 1.0 configuration protocol, and NOX API V2
Delivered. Openflow-1.0 branch Yes
S2.e Support campus installations of GENI software with AM API
Ongoing (no finite end) Yes
S2.f Port existing applications to latest OpenFlow identifiers
Delivered. Released transition notes and work with individual teams to port their apps
Yes
S2.g Add support for multiple Openflow protocols Not planned for -
S2.h Increase portability Delivered. Published guide for porting to CentOS and reduced dependency
Yes
S2.i Release 1st ver SNAC/NOX console software Delivered. Also in NOX-destiny. Yes
S2.j Plan and engineer GEC 9 demo Ongoing Yes
S2.k Support campuse upgrades to OF 1.0 and GENI API
Delivered. All campuses transitioned Yes
S2.l Improve system and regression test support Ongoing Yes
S2.m Publish feature list for 2011 releases Ongoing Yes
25-Aug-2010
Sponsored by the National Science Foundation 33
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
Sponsored by the National Science Foundation 34
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
Sponsored by the National Science Foundation 36
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
Sponsored by the National Science Foundation 37
GEC9 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/Internet2
– Perform dry-runs and testing for GEC9– Polish demos
• Tech support for other campuses– Help transition software to latest supported version
25-Aug-2010
Sponsored by the National Science Foundation 38
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
Sponsored by the National Science Foundation 39
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