1 / 16

Automated GOLEs and Fenius : Pragmatic interoperability

Automated GOLEs and Fenius : Pragmatic interoperability. Winter Joint Techs 2011 Clemson, SC. Evangelos Chaniotakis, ESnet Network Engineer Lawrence Berkeley National Lab. Introductions. GLIF: Global Lambda Integrated Facility Many participants: NRENs , exchanges, sites, companies

prue
Download Presentation

Automated GOLEs and Fenius : Pragmatic interoperability

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. Automated GOLEs and Fenius: Pragmatic interoperability Winter Joint Techs 2011 Clemson, SC Evangelos Chaniotakis, ESnet Network Engineer Lawrence Berkeley National Lab

  2. Introductions • GLIF: Global Lambda Integrated Facility • Many participants: NRENs, exchanges, sites, companies • GOLE: GLIF Open LightpathExchange • Many GLIF participants operate a GOLE • Automated GOLE Task Force • Founded in 2010 with the objective of automating lightpath provisioning across multiple GOLEs • Current chair: Jerry Sobieski • Close collaboration with GNI API Task Force, OGF NSI, NML • GNI API Task Force: • Founded in 2008 with the objective of developing a common API between circuit provisioning services • Chair: Evangelos Chaniotakis

  3. GLIF map

  4. Motivation • The research community has a global, well connected “network of networks” • Many networks provide some circuit-oriented service, • And, it is becoming increasingly common for these circuits to be “stitched” across multiple networks, SC09: ~20 L2 circuits. SC10: ~50, SC11: ? • Stitching these “by hand” is slow – and cuasesss errors. • Software does exist to automate circuit provisioning.... • But it generally doesn’t work when stitching, • Because we don’t have a common provisioning toolkit

  5. Fenius A simplecommon provisioning API and toolkit + Just good enough to support common stitching case today, + Software that implements it, + That works with existing provisioning software, + Motivation for network operators to deploy & operate, = (the potential for) Global Interoperability

  6. Automating the GOLEs • Several GOLEs committed network and human resources for a one-year test drive of automation, • The Fenius software project by GNI API Task Force was decided be used as a thin interoperability layer. • Fenius instances were deployed to Automated GOLE sites • The various NRMs were configured to work with Fenius, • Topology information was collected, • PerfSONARPingER nodes are deployed to test the data plane • Weekly calls to keep the project alive & kicking

  7. Automated GOLE Deployment • Asia: • JGN2+, AIST, KDDI • USA: • ESnet SDN, Internet2 ION & MANLAN, • StarLight, USLHCnet, Caltech • Europe: • Netherlight, CERNLight, University of Amsterdam, • NorthernLight, PSNC, CERNLight,

  8. Global Deployment

  9. PingER Demonstration JGN2+ PingER JGN2+ PSNC PingER StarLight, USLHCnet, Internet2ION, NetherLight, PSNC KDDI KDDI PingER UvA PingER

  10. Demonstration control plane JGN2+ PingER JGN2+ IDC PSNC PingER StarLightArgia, USLHCnet IDC, Internet2ION IDC, NetherLight DRAC, PSNC, KDDI G-Lambda KDDI PingER UvA PingER Fenius SuperAgent

  11. Demonstration

  12. Fenius Components • Common provisioning API over web services, • Translation framework for Java (optional) • Translators for IDC, G-lambda, Harmony, dynamicKL • Native implementation in OpenDRAC, • Scriptable command-line client • Web UI “Superagent” with topology and pathfinding • Monitoring and visualization (in progress)

  13. Translation Framework Common API G-lambda Translator G-lambda Common Web UI Client Common API Common Command-Line Client IDC Translator IDC Common Monitoring Client DRAC Common API

  14. Challenges and lessons learned • Be enthusiastic and believe in your project • Getting collaborators interested can be difficult • Get buy-in from their management • Resources can be unreliable • Get buy-in from their management (and yours) • Remember to account for differences in time zones, language, culture • Once project gains momentum, keep the ball rolling • Keep away from politics • Make sure everyone has a chance to contribute • You will need to work long hours

  15. Future directions • Deploy in more networks, • Implement missing features, • Extend API and toolkit (keeping it simple!), • Gain support from more network management software, • Harden software & make it operational, • Improve user interface • Better documentation • Take over the world! :)

  16. Special Thanks • Gerben van Malenstein • EdoardoMartelli • Takahiro Miyamoto • AzherMughal • Fumihiro Okazaki • Jan Radil • JordiFerrerRiera • SandorRosza • Ryousei Takano • Thomas Tam • Jin Tanaka • Alan Verlo • John Vollbrecht • Fred Wan • Xi Yang • Frank Blankman • Scott Campbell • Joan Garcia Espin • John Graham • Jeroen van der Ham • Takatoshi Ikeda • Nils Jacobson • GigiKarmous-Edwards • Tomohiro Kudoh • Kavitha Kumar • Ali Lahlou • Andrew Lake • Tom Lehman • Mathieu Lemay • John MacAuley

More Related