1 / 15

Workshop on Prototyping and Deploying Software Defined Exchanges

Workshop on Prototyping and Deploying Software Defined Exchanges. Chip Elliott, BBN / GENI June 5, 2014. Workshop Goals. Follow-on to December 2013 workshop Develop prototypes / deployment strategies Software Defined Exchanges ( SDXs ) for multi-domain Software Defined Networks ( SDNs )

marie
Télécharger la présentation

Workshop on Prototyping and Deploying Software Defined Exchanges

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. Workshop on Prototyping and Deploying Software Defined Exchanges Chip Elliott, BBN / GENI June 5, 2014

  2. Workshop Goals • Follow-on to December 2013 workshop • Develop prototypes / deployment strategies • Software Defined Exchanges (SDXs) • for multi-domain Software Defined Networks (SDNs) • and Software Defined Infrastructure (SDI) • We expect national / regional deployment of experimental SDXs of varying capabilities(e.g. ‘n’ instances as per December workshop)

  3. Early days for “SDX”

  4. Agreeing on One or More SDX Models • “Near-term” SDX – pure connectivity • Layer 3 (IP) – e.g. connect AS’s • Layer 2 (Ethernet) – e.g. multi-domain circuits • SDN – connect SDN islands • “Advanced” SDX – with compute/storage • Connect SDI islands • Compute / storage / network • GENI as an early instance

  5. Workshop Charge • For both “Near-term” and “Advanced” SDXs . . . • Create slides to form the basis for a workshop report • One or more conceptual SDX architectures • SDX functionality, ideally with one or more exemplar applications • Identify key issues (e.g. trust, authentication, authorization, interoperability, testing) • Specify staged set of research / prototyping activities • Provide strawman plan, with level of effort, for experimenting with national scale SDX deployment

  6. Agenda • Today (now till 6 PM) • Initial presentations • Two break-outs (Near-term, Advanced) that will each create slides as above • Reconvene for both presentations / discussion • Break out again for further refinement • Tomorrow (8:30 – 1:00) • Convene for revised presentations / discussion • Break out to finalize slides • Reconvene for final presentations / discussion • Call for Volunteers

  7. “Advanced SDXs”and Software Defined Infrastructure(my perspective)

  8. Where I am coming from - GENI Fundsin hand Need funding Self funding As of 2/2014 We’re building out GENI through universities across the US

  9. Slices and deep programmability Install the software I want throughout my network slice (into firewalls, routers, clouds, …) And keep my slice isolated from your slice, so we don’t interfere with each other We can run many different “future internets” in parallel

  10. Slices span many organizational boundaries My experiment runs acrossthe evolving GENI federation. Campus#3 Commercial Clouds Backbone #1 Campus My GENI Slice Corporate GENI suites Access#1 Backbone #2 Research Testbed This approach looks remarkably familiar . . . Other-Nation Projects Campus#2 NSF parts of GENI Goals: avoid technology “lock in,” add new technologies as they mature, and potentially grow quickly by incorporating existing infrastructure into the overall “GENI ecosystem”

  11. Major trends are converging Software Defined Infrastructure Multi-tenant Datacenters Software Defined Networks Distributed Datacenters Network Functions Virtualization (NFV)

  12. We’re all heading to the same place Fast spin new protocols, switching strategies, virtual machines Rapidly create entire “sliced”cyberinfrastructure / networks on demand Clouds Grid Ofelia Software defined networks Vnode US Ignite Network functions virtualization FLARE Wivi GENI Inter-cloud

  13. Instantiating services into slices Thousands of parallel slices • Soon each switching point will be able to sustain 10,000 – 100,000 slices • Can run arbitrary software in each slice • Decoupling of “service” from infrastructure

  14. “Advanced SDX” • A) Slice peering point – • Where slices cross administrative domains • An inter-cloud meeting point • But not just connectivity . . . • . . . also includes“for rent” (multi-tenant) compute / storage in addition to connectivity • B) Service deployment point • Great place to instantiate certain kinds of service, e.g., middle boxes, load balancers, measurement, content delivery, video translation, etc.

  15. Conceptual sketch Cloud B Cloud A Cloud C Advanced SDX

More Related