Upload
myrtle-reed
View
216
Download
3
Embed Size (px)
Citation preview
Sponsored by the National Science Foundation
Meso-scale Integration
Heidi Picher DempseyNovember 17, 2009
www.geni.net
Sponsored by the National Science Foundation 2November 17, 2009
Outline
• Meso-scale motivation and projects• Data and control plane examples• Getting involved
"Human felicity is produced not so much by great pieces of good fortune that seldom happen, as by little advantages that occur every day." Autobiography of Ben Franklin
Sponsored by the National Science Foundation 3November 17, 2009
Meso-scale integration builds on successful prototypes
Ongoing spiral development and prototyping
Ope
nFlo
wW
iMax
“At scale”Enables at-scale research via reliable, easy-to-use software running on many suites of GENI-enabled infrastructure
Decision points
“Meso-scale”Explores and permits realistic evaluations of research utility, cost, …
“The frontier”Wide open to new ideas & innovations
Nex
t pro
ject
s
Sponsored by the National Science Foundation 4November 17, 2009
Meso-scale infrastructure goals
Year 1 (2009-2010) Year 2 (2010-2011) Year (20011-2012)
•GENI-enabled backbone deployments in I2 and NLR
•Some early experiments •More Experiments
•OpenFlow Campus deployments
•Some production traffic on GENI
•More Production Use
•Early WiMax Deployments •Complete WiMax Deployments
•Some Educational Use
Sponsored by the National Science Foundation 5November 17, 2009
GENI toolbox for meso-scale integration
• First steps with some Spiral 1 projects: ProtoGENI nodes, OpenFlow and PlanetLab integration, BGP Mux
• Next steps with new Spiral 2 projects: – 12 OpenFlow deployment projects in campuses and
nationwide network – 7 WiMax campus deployment projects– 1 ShadowNet backbone instrumentation project– 1 Quilt regional networking project.
• Other projects also provide key parts of meso-scale integration: security, monitoring, tools, clearinghouses
Sponsored by the National Science Foundation 6November 17, 2009
• More meso-scale prototypes for access control, authentication, and full-scale GENI security architecture. See the Control Framework working group meeting on Wednesday (Rob Ricci, Jeff Chase chairs) and the OMIS working group meeting on Tuesday (Jim Williams, Ivan Seskar, Ron Hutchins chairs).
• More meso-scale prototypes for instrumentation. See the Instrumentation & Measurement working group meeting on Wednesday (Paul Barford chair)
• A GENI API that allows aggregates to use any GENI control framework with resource specifications as parameters.
We need more!
an sfa-like possibility (one of many)an sfa-like possibility (one of many)
links, pix?
Sponsored by the National Science Foundation 7November 17, 2009
Meso-scale overview: sites
ClemsonColumbia UniversityGeorgia Tech Indiana UniversityInternet2National Lambda RailNicira Networks (software only)Polytechnic Institute of NYUPrinceton UniversityRutgers University
Commercial vendors like HP and NEC
StanfordUniversity of ColoradoUniversity of KentuckyUniversity of MassachusettsUniversity of WashingtonUniversity of WisconsinUCLA
Sponsored by the National Science Foundation 8November 17, 2009
Integration overview: projects
Principal Investigators and Co-PIs
Industry Partners Proposed Sites (locations subject to change)
Enterprise GENI Campus Trials
Nick McKeown and Guru Parulkar, Stanford
Nicira Networks, HP, Arista, Cisco, Juniper, NEC, others
8 (Clemson, Georgia Tech, Indiana U, Princeton, Rutgers, U Wisconsin, U Washington, Stanford)
OpenFlow Backbone Deployment in Internet2
Randy Frank and Eric Boyd, Internet2
TBD 5 (Atlanta, Houston, Kansas City, Salt Lake City, Washington D.C.)
OpenFlow Backbone Deployment in NLR
Glenn Ricart and Wendy Huntoon, National Lambda Rail
TBD 4-5 (Atlanta, Chicago, Denver, Seattle, Sunnyvale)
ShadowNet Backbone and Instrumentation Deployment in Internet2
James Griffioen and Zongming Fei, U. Kentucky, Jacobus van der Merwe, AT&T Research
Juniper, AT&T Research, 4 (Atlanta, Kansas City, Salt Lake City, Washington, D.C.)
WiMax Campus Deployment Dipankar Raychaudhuri, Ivan Seskar, Smapath Rangarajan, Rutgers University
NEC laboratories, America, Cisco
8 (Columbia, Polytechnic U of NYU, Rutgers, Stanford, UCLA,, U of Colorado, Boulder, UMass Amherst, U of Wisconsin)
Regional Networks in GENI Jen Leasure, The Quilt none N/A
Sponsored by the National Science Foundation 9November 17, 2009
Current OpenFlow
•Allocate PL compute resource slices with PlanetLab Aggregate Manager (assume authentication registry)•Allocate and configure topology slices with Enterprise GENI Aggregate Manager and OpenFlow FlowVisor •Manage experiments with Experiment Controller and SFI tools
SFI/CH
PLC
PlanetLab Aggregate Manager
AuthentRegistry
Exptr Key Authentication
Get Resources
Resource list
Create Slice
Princeton
Tunnel
OpenFlow switches
Resource list
Create Slice
Get Resources E-GENIAggregate Manager FlowVisor
Slice creation
Topology
Expt A controller
OpenFlow protocol
PlanetLab nodes
Stanford
Sponsored by the National Science Foundation 10November 17, 2009
Current WiMax
•Access Rutgers base station and clients through ORBIT•Configure experiments with OMF•Planning seven more campuses connected with with L2/3 networks (Some campuses also have OpenFlow switches.)•Allocate slices and configure experiments with GENI control framework (TBD) and OMF
Rutgers Universit
y
Sponsored by the National Science Foundation 11November 17, 2009
ShadowNet
• Add Juniper m7i routers as forwarding components of some ProtoGENI I2 nodes
• Configure logical "shadow" routers with protocols, Forwarding Information Base and reporting
• Make slice-specific instrumentation information available to experimenters
ProtoGENI node in I2
Sponsored by the National Science Foundation 12November 17, 2009
Integration overview: new users
• What do prototype teams need to support rapid builds and deployment to new users?
• How do we organize GENI support with more networks and more users?
• How well do prototypes work with more sites and users?• What do campus IT staff and network operators need to
support simultaneous production and experimental use?• How will new users bring "real" traffic to GENI?• What do experimenters need?• Who will use GENI?
Sponsored by the National Science Foundation 13November 17, 2009
Why OpenFlow and VLANs?
• OpenFlow has very active commercial product support (required for most campus deployments)
• Ethernet VLANS are implemented nearly everywhere already (although different varieties)
• It's fairly inexpensive for a project to add switches and configure VLANs
• Widespread deployment possibilities result in more layer 2 end-to-end substrates for experiments
• This is only an interim solution• GPO is interested in other projects with meso-scale
potential
Sponsored by the National Science Foundation 14November 17, 2009
Longer-term GENI solutions
• Dynamic experimenter-controlled GENI topology slices and related applications
• Build your own ISP: BGPMux in a slice• Dynamic optical switching tied to applications and network
layer software• Models for how to manage, monitor and operate user
slices in production networks (enable custom services built on custom networks)
• Commercial vendor support for virtualization at all levels in networks
• "Frontier" projects like cross-layer optical and cognitive radio may eventually transition to meso-scale
Sponsored by the National Science Foundation 15November 17, 2009
Meso-scale data and control planes
Engineer control and data paths through multiple campus, regional, and backbone infrastructures for nationwide GENI connectivity.
Sponsored by the National Science Foundation 16November 17, 2009
Data plane Options
NLR FrameNet service with VLAN mapping in use now for RENCI/Duke connections
VLAN tunnels (q-in-q) in use now for University of Utah connections to ProtoGENI nodes
Sponsored by the National Science Foundation 17November 17, 2009
Data plane Options
ION (DCN) service on Internet 2 (not GENI wave) (see connectors at http://www.internet2.edu/ion/connector-status.html)
GMPLS (DRAGON, MAX, ISI)
Sponsored by the National Science Foundation 18November 17, 2009
Meso-Scale Prototyping: Clemson Example
• Scope: Integrate Clemson campus Ethernet switches, wireless mesh access points with mobile terminals, and local Network Operations Center (with production traffic) into GENI. Work with 7 other GENI campus trials.
• Initial proposal: Campus-centric three-task Clemson deployment plan• Preliminary network investigation
– Multiple data and control plane options– Integration with NLR and I2 both feasible– Good operations component, but not integrated with GENI Meta NOC– Campus features production traffic, active measurement, and good existing policy
framework, but needs integration with GENI security and measurement projects– Coordinate deployment with other campus trials
Sponsored by the National Science Foundation 19November 17, 2009
Meso-Scale Prototype Integration: Clemson Example
CTO/PI Campus Infrastructure Plan
Integrate with ResearchInfrastructure, GENI projects
Engineer IP networks(control and data)
Integrate with I2 Infrastructure
Integrate with NLR Infrastructure
Integrate Policy, Security and Operations
Bring Clemson's original deployment plan (white) into larger-scale GENI integration and deployment (tan), benefitting both.
Sponsored by the National Science Foundation 20November 17, 2009
Building the GENI Meso-scale PrototypeCurrent plans for locations & equipment
WiMAX
ShadowNet
Salt Lake CityKansas City
DCAtlanta
StanfordUCLAUC BoulderWisconsinRutgersPolytechUMassColumbia
OpenFlowBackbonesSeattleSalt Lake CitySunnyvaleDenverKansas CityHoustonChicagoDCAtlanta
OpenFlowStanford
U WashingtonWisconsin
IndianaRutgers
PrincetonClemson
Georgia Tech
Arista 7124S SwitchCisco 6509 Switch
HP ProCurve 5400 Switch
Juniper MX240 EthernetServices Router
NEC IP8800 Ethernet Switch
NEC WiMAX Base Station
Sponsored by the National Science Foundation 21November 17, 2009
Meso-Scale Infrastructure Integration Steps
•Some common steps for all Spiral 2 Meso-scale projects (old and new)
Task Name Schedule
GEC DemonstrationsAs scheduled--Integration focus is March and October
GENI Integration Software Releases December and July each year
GENI Integration Security Reviews January and August each year
Project Functional Goals Project kickoff + 1 mo, review yearly
Project Spiral Integration Plan Project kickoff + 1 mo, review yearly
Project Integration Risk Register Project kickoff + 1 mo, review yearly
Project Contacts join GENI Prototype Response and Escalation group
1 month before first external deployment or software release (not an isolated testbed)
Sponsored by the National Science Foundation 22November 17, 2009
Detailed Integration Plans: OpenFlow Campuses and Connections to GENI
Year 1 Year 2 Year 3 (or earlier)
•Create OpenFlow Planning Group
• 8 campus demo •Capstone Demo
•OpenFlow Tutorials •Additional U Washington deployments•Deploy U Wisconsin (campus)
•Add Clemson wireless mesh to campus deployment
•Deploy Clemson, Georgia Tech, Indiana, Princeton, Rutgers, U Wisconsin (testbed), U Washington (Stanford pre-existing)
•Production Traffic at Clemson, Indiana, Princeton, Rutgers•Rutgers ORBIT virtualization (tesbed)•Rutgers early experiments
•Rutgers educational use
•First OF Access at Indiana, Princeton, U Wisconsin (testbed)
•First OF Access at Georgia Tech, U Washington, U Wisconsin
•First Indiana Monitoring and Measurement Access
•U Washington Experiments
•Princeton User Opt-In Software•U Wisconsin Measurement and Management Software
•U Wisconsin opt-in and slice management software
Highlights Selected Details
Yellow rows show suggested intermediate steps. white are from original proposal.
Sponsored by the National Science Foundation 23November 17, 2009
Detailed Integration Plans: OpenFlow in NLR, Internet2
Year 1 Year 2 Year 3•OpenFlow deployment in Internet 2
• First community I2 OF backbone node access
•OpenFlow Regional Connections
•Early Experiments
•Experiments
Internet2 Highlights Selected Details
Year 1 Year 2 Year 3•OpenFlow Deployment in NLR
• First Community NLR backbone node access with OpenFlow
•OpenFlow Regional Connections
•Early Experiments
•Experiments
NLR Highlights
Sponsored by the National Science Foundation 24November 17, 2009
Detailed Integration Plans: WiMax Campuses and connections to GENI
Year 1 Year 2 Year 3•Deploy U Massachusetts, Amherst NYU Polytech
•3 campus WiMax demo•Deploy U Wisconsin. UCLA, Columbia, Colorado
•6 campus demo
•First Community WiMax access at Rutgers (base station already deployed in Spiral 1)
•NYUP testbed development•UMass testbed integration•UCB site measurements
•First WiMax access at NYUP, U Wisconsin, UCLA, UCB, Columbia
First Community WiMax access at Rutgers (base station already deployed in Spiral 1)
•UMass production traffic
•UCB experiments•Columbia education use•Columbia early experiments
Highlights Selected DetailsOpen WiMax. Integrate WiMax base stations with GENI and deploy to multiple campuses 1. Acquire and deliver equipment kits to each participating campus (campuses fund their own projects)2. Software updates, coordination with OMF (AM and Clearinghouse)
Develop installation and operations guidelines for campus WikMax RutgersProcure and deliver WiMax base station kits to UMASS Amherst and NYU Polytech NEC + RutgersTesting with GPO (staging w/out radio) NEC + Rutgers +GPOProcure and deliver WiMax base station kits to NYU Polytech NEC + RutgersProcure and deliver WiMax base station kits to UC Boulder NEC + RutgersProcure and deliver remaining WiMax base station kits to 3 campuses (serially) NEC + RutgersUpgrade WiMax base station controller software (GBSN v3.0) NEC + Rutgers
Sponsored by the National Science Foundation 25November 17, 2009
Detailed Integration Plans: ShadowNet backbone in Internet2
Year 1 Year 2 Year 3•Deploy 3 ShadowNet routers
• Deploy 4th ShadowNet router
•First (GENI) Community PerfSONARAccess
•Integrate the virtualized Juniper router control software into protoGENI
First ShadowNet Archive Access
Early Experiments and Measurements
•Experiments and Measurements
Highlights Selected DetailsShadowNet
Install Juniper Routers in I2 PoPs Must be ProtoGENI PoPs. I2 lead.Extend Shadowbox control software for GENI virtualization. Integrate with CF for slices.
AT&T lead. Virtual routers in GENI slices,
Develop measurement toolsets UKY lead. AT&T secondary.Incorporate perfSONAR UDel lead Integrate ShadowBox measurement tools with ProtoGENI UKY lead. Utah secondary
Store and Archive Shadowbox data
May be possible earlier, but must be by this point. Includes Juniper router data and experiment data.
Enable DCN measurement plane I2 leadGENI community access to Juniper router slices GPOEnd-to-end router tests/experiments GPO + Early adoptersEnd-to-end measurement tests/experiments GPO + Early adopters
Sponsored by the National Science Foundation 26November 17, 2009
• Experimenters: use the meso-scale infrastructure for experiments — engineering and operations help is available
• Campuses: New campuses can join the meso-scale work. Talk to the PIs or the GPO
• Prototyping teams: user GUIs, monitoring and security tools and interfaces that support slices and virtualization. Meso-scale may be good test environment for some tools.
• Network engineers: help GENI define scalable kits and processes, provide regional workshop inputs (via the Quilt)
• Industry: new sites can join meso-scale, meso-scale may provide
good test environments for commercial-bound systems.
How can I get involved?
Sponsored by the National Science Foundation 27November 17, 2009
Start dreaming
• Spiral 2 adds lots of programmable infrastructure to GENI
• We need creative ideas for how to use it• Some projects are already doing mash-ups– live
demos coming up next• With ORBIT, K-GENI, and OpenFlow
deployments, GENI will circle the globe.• Can we send a virtual model train around GENI's
world to drive the GENI "golden spike?"• Better ideas?
Sponsored by the National Science Foundation 28November 17, 2009
• OpenFlow-PlanetLab. Rob Sherwood, Srini Seetharaman, Jad Naous, Guido Appenzeller (Stanford), Sapan Bhatia, Andy Bavier (Princeton)
• ORBIT and WiMax Base Station. Ivan Seskar (Rutgers)
• ProtoGENI Cluster. Robert Ricci (University of Utah)
Integration and Meso-scale demos