280 likes | 588 Views
Meso-scale Integration. Heidi Picher Dempsey November 17, 2009 www.geni.net. Outline. Meso-scale motivation and projects Data and control plane examples Getting involved.
E N D
Meso-scale Integration Heidi Picher DempseyNovember 17, 2009 www.geni.net
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
Meso-scale integration builds on successful prototypes “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, … OpenFlow WiMax Next projects “The frontier” Wide open to new ideas & innovations Ongoing spiral development and prototyping
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
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! links, pix? an sfa-like possibility (one of many)
Meso-scale overview: sites Clemson Columbia University Georgia Tech Indiana University Internet2 National Lambda Rail Nicira Networks (software only) Polytechnic Institute of NYU Princeton University Rutgers University Commercial vendors like HP and NEC Stanford University of Colorado University of Kentucky University of Massachusetts University of Washington University of Wisconsin UCLA
Current OpenFlow PLC PlanetLab Aggregate Manager Exptr Key Authentication • 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 AuthentRegistry SFI/CH Get Resources Resource list Create Slice E-GENIAggregate Manager Get Resources Topology Resource list FlowVisor Create Slice Slice creation Expt A controller OpenFlow protocol Princeton Stanford Tunnel OpenFlow switches PlanetLab nodes
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 University
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
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?
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
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
Meso-scale data and control planes Engineer control and data paths through multiple campus, regional, and backbone infrastructures for nationwide GENI connectivity.
Data plane Options VLAN tunnels (q-in-q) in use now for University of Utah connections to ProtoGENI nodes NLR FrameNet service with VLAN mapping in use now for RENCI/Duke connections
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)
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
Meso-Scale Prototype Integration: Clemson Example Bring Clemson's original deployment plan (white) into larger-scale GENI integration and deployment (tan), benefitting both. Engineer IP networks (control and data) Integrate with Research Infrastructure, GENI projects CTO/PI Campus Infrastructure Plan Integrate with NLR Infrastructure Integrate with I2 Infrastructure Integrate Policy, Security and Operations
Building the GENI Meso-scale PrototypeCurrent plans for locations & equipment OpenFlow WiMAX Stanford U Washington Wisconsin Indiana Rutgers Princeton Clemson Georgia Tech Stanford UCLA UC Boulder Wisconsin Rutgers Polytech UMass Columbia OpenFlow Backbones ShadowNet Seattle Salt Lake City Sunnyvale Denver Kansas City Houston Chicago DC Atlanta Salt Lake City Kansas City DC Atlanta Juniper MX240 Ethernet Services Router HP ProCurve 5400 Switch NEC WiMAX Base Station Cisco 6509 Switch NEC IP8800 Ethernet Switch Arista 7124S Switch
Meso-Scale Infrastructure Integration Steps • Some common steps for all Spiral 2 Meso-scale projects (old and new)
Detailed Integration Plans: OpenFlow Campuses and Connections to GENI Highlights Selected Details Yellow rows show suggested intermediate steps. white are from original proposal.
Detailed Integration Plans: OpenFlow in NLR, Internet2 Internet2 Highlights Selected Details NLR Highlights
Detailed Integration Plans: WiMax Campuses and connections to GENI Selected Details Highlights
Detailed Integration Plans: ShadowNet backbone in Internet2 Highlights Selected Details
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?
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?
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