Internet2 Network: Controlling a Slice of the Na6onal Network. Eric Boyd Senior Director of Strategic Projects

Transcription

1 Internet2 Network: Controlling a Slice of the Na6onal Network Eric Boyd Senior Director of Strategic Projects

2

3 I2 Production User I2 Prototype Internet2 Taxonomy Implemented Using LHCONE NET+ External Provider s Dependencies XSEDE GENI? Layer 3 R&E IP and TR-CPS s I2-Run Specific Hardware Connectors GENI Learning ONOS? General Purpose VLAN - AL2S SDN Controller ESNET NOAA NVS (Network ization ) ized Ethernet ing Hypervisor Ethernet es Circuits and Wavelengths - AL1S Fiber & Optical Transport

4 Network iza<on on Internet2

5 Network iza<on on Internet2

6 Network iza<on on Internet2

7 Network iza<on on Internet2 Control a slice of the na<onal network! Enable: Rapid prototyping of advanced applica<ons Rapid prototyping of new network services Rapid advancement of network research

8 KEY OpenFlow Internet2 Software Stack Experimenter Code EXP APP FOAM STITCHING AGGREGATE UI EXP APP API API API API NSI API GENI Learning MD- NOX NOX NSI OSCARS NSI IDCP OpenFlow FIU FSFW Utah FSFW MAX FSFW OpenFlow OpenFlow OpenFlow OpenFlow OpenFlow OpenFlow OpenFlow OpenFlow

9 Internet2 March, 2015 Current Status Aggregate Manager in produc<on Hypervisor (FlowSpace Firewall) in produc<on Accep<ng 3 rd party controllers Ques<onnaire Test Lab Produc<on Support L2 and L3 matching FSFW Updates (current version 1.0.4a) Vendor Updates (current versions Juniper 13.3, Brocade 5.6dc) Vendor- specific limits do exist. OpenFlow 1.0 Supported

10 Controlling a Slice on Internet2 Request a slice ( [email protected]) Receive a ques<onnaire from Internet2 NOC Submit ques<onnaire to Internet2 Download FSFW; try your controller in that environment hdp://globalnoc.iu.edu/sdn/fsfw.html/ Submit your package Good documenta<on accelerates process! Good logging accelerates process! Internet2 NOC tests your controller on idream GENI environment Problems - > Go back one step Internet2 deploys your controller on Internet2 Network

11 What do we want you to do Have well tested, well versioned, and packaged code Provide lots of documenta<on Provide lots of configurable logging Have a Ticke<ng/Bug repor<ng system Provide Installa<on and Opera<on instruc<ons Given the FlowSpace be able to generate the proper Configura<on for your applica<on Be pa<ent, it s a learning experience for all of us

12 What do you need to do Provide Enough documenta<on to setup and configure your applica<on Provide enough logging (to a file) to be able to debug your applica<on If it breaks we will disable your slice, and send you the log, your slice will not be enabled un<l the problem is fixed Any API (besides OpenFlow) or UI must be secure Provide involved and reac<ve developers Applica<on should already have been tested with FlowSpace Firewall to verify it will func<on properly FlowSpace Firewall does not re- write rules, it allows or denies rules. Your app needs to be able to work on a set of VLANs (and they wont be the same VLAN across all devices) Know the FlowSpace you want for your slice es EndPoints Number of flows Interfaces

13 FAQs I don t have a Brocade or Juniper. Can I develop on the idream GENI plamorm? No, not really. It s a limited resource with a <ght schedule. See if you can find a Juniper or Brocade elsewhere to validate controller func<onality. Tes<ng on v is not the same as tes<ng on real world es. Despite the vendor- agnos<c promise of OpenFlow, be prepared to have vendor- specific details in your controller. Am I controlling produc<on traffic? No, you are controlling your slice. You need to generate traffic into the slice. Am I running my controller? No, the Internet2 NOC is running your controller in a private slice. Make sure the logging is good enough that you can figure out what went wrong. Packaging? Documenta<on? Logging? This is a research project. I just wrote the controller yesterday, and most of the configura<on details in my head. The Internet2 NOC is deploying and running your controller and feeding you the logging results. The beder the packaging, documenta<on, and logging, the more likely your effort will be a success. How good is your OpenFlow 1.3 support? Very good, if you mean OpenFlow 1.0. Otherwise, we re not there yet. My controller requires 10 bare metal servers to run. Internet2 has a very limited number of servers on which we can deploy controllers. Please planto minimize your configura<on or supply servers we can deploy.

14 Internet Plans Work with vendors to get OF 1.3 Support Brocade - > 5.8x ( now ) Juniper - >? ( summer ) Work to update sotware stack FSFW Update (needed to support OF 1.3) Update (needed for QoS, QnQ) Refine Slice Deployment Process Faster? Tes<ng constraints? Define Opera<onal Hardware Environment Less scrabbling for boxes

15 Prototype Mul<- Domain Layer 2 Backdrop: Internet2 operates a Layer 2 Campuses (e.g. University of Utah) operate a Layer 2 Regional Networks (e.g. MAX) operate a Layer 2 Exchange Points (e.g. AMPATH/FIU) operate a Layer 2 Is there a way to create a Mul<- Domain Layer 2? Common capabili<es Willingness to collaborate Willingness to contribute to a common project Maintain local control Withdraw at any <me Enable (illusion of) global control Control remote administra<ve domains No change in sotware, just configura<on

16 SDX SDX1

17 SDX SDX1 SDX2 SDX3

18 SDX NSI NSI NSI SDX1 SDX2 SDX3

19 Multi-Domain SDX SDX1 SDX2 SDX3

20 Multi-Domain SDX SDX2 SDX3

21 Multi-Domain SDX GENI Controller SDX2 SDX3

22 Multi-Domain SDX FlowSpace Firewall SDX2 SDX3

23 Multi-Domain SDX SDX2 SDX3

24 Multi-Domain SDX SDX2 SDX3

25 NORDUnet Multi-Domain SDX Internet2 SDX2 SDX3

26 MD - Utah MAX Multi-Domain SDX Internet2 FIU

27

28 Mul<- Domain Sample Network Utah 3505 HP PS HP PS FIU Internet2 AL2S MAX PS Brocade Brocade Brocade PS PS Brocade DELL Brazil PS 3502

29 Interna6onal SDN Testbeds What are we trying to achieve?

30 Testbed vs. Produc<on? Why are we talking about testbeds? What are the barriers to using SDN in produc<on?

31 What are the goals of a testbed? Support network research? Explore new network paradigms in prepara<on for transi<on to produc<on?

32 Why should testbeds interoperate? Demonstrate general connec<vity while implemen<ng underlying connec<vity in unique ways? Support mul<- domain network research? Prepare for transi<on to produc<on in a mul<- domain environment?

33 How should testbeds interoperate? Orchestra<on through exis<ng interoperability mechanisms (e.g. BGP, NSI, GENI S<tching, etc.) Orchestra<on through new paradigms (e.g. ONOS)

34 What charge should we give? Interna<onal SDN Testbeds FTW is next week. What would the GLIF Tech group like to see in the way of outcomes?