1 / 9

GENI SDN Offering

GENI SDN Offering. Marshall Brinn, GPO GEC18: October 28, 2013. Outline. Introduction Speakers: Eric Boyd, Internet2 Nick Bastin , Barnstormer Softworks Discussion: Planning to build the GENI SDN Offering. GENI’s SDN Offering to Experimenters.

annot
Download Presentation

GENI SDN Offering

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. GENI SDN Offering Marshall Brinn, GPO GEC18: October 28, 2013

  2. Outline • Introduction • Speakers: • Eric Boyd, Internet2 • Nick Bastin, Barnstormer Softworks • Discussion: Planning to build the GENI SDN Offering

  3. GENI’s SDN Offering to Experimenters • GENI offers experimenters a “user-specified programmable WAN” capability • A collection of resources networked in a user-specified manner (links, subnets) • An ability to program the forwarding decisions for traffic flowing across this WAN • The traffic on this WAN is logically segregated from traffic on other such WANs (slices) • The traffic on this WAN is visible through standard network monitoring tools (e.gtcpdump) We want to make simple things simple, common things easy, and cutting-edge things possible.

  4. Speakers • Nick Bastin, Barnstormer Softworks • A Model for providing S/W switch-based programmable WAN for experimenters • Eric Boyd, Internet2: • Current plans and expected features for I2 offering in support of GENI SDN offering

  5. Uniform approach to SDN-enabled Topologies • We seem to have two different approaches • An approach based on slicing H/W switches • An approach based on distinct S/W switches • I want to advocate for a uniform approach, from an experimenter’s perspective • Much like other resource allocation, you ask for what you want and you get the resources that match that request • If you want a H/W switch for your experiment, you should get a H/W configuration • If you want to work e.g. with IPv6 or OF1.3+, you should get a S/W configuration • If you don’t specify, you should get whatever is convenient and available for aggregates to provide

  6. Configuration: End-to-End Programmability A stitched topology of resources connected through the backbone network aggregate provides SDN controllability of all hops between edge aggregates. Agg Agg Agg Backbone Network Agg Agg Agg Agg Agg

  7. Configuration: Aggregate-internal SDN-enabled LAN Aggregate TOR FV VM-1 Controller VM-2

  8. Configuration: Edges ARE Hops Consider all the edge aggregates as logically connected in a mesh. Any given topology is constructed from that mesh with intermediate OF-controllable hops at other edge aggregates. Agg Agg Agg Agg Agg Agg Agg

  9. Discussion: Moving forward • I want to see both of these approaches move forward to fruition and be available to experimenters as soon as possible • What can we (the GENI community) do to make these available? • What the the critical roadblocks we should focusing on solving? • How do we transition from current meso capability to future SDN capabilities? • Is the notion of a uniform approach feasible and desirable? • When can we have prototypes of these different capabilities? • What phasing of capabilities is possible (some soon, more later)

More Related