Campus/Experiment Topics in Monitoring and I&M GENI Engineering Conference 15 Houston, TX

1. Campus/Experiment Topics in Monitoring and I&MGENI Engineering Conference 15Houston, TX Sarah Edwards Chaos Golubitsky Jeanne Ohren October 23, 2012 www.geni.net

2. Introduction Instrumentation, Measurement, and Monitoring • These tools provide visibility into the state of: • GENI experiments and slices • Operational GENI resources, campuses, and aggregates • GENI-controlled networks, and non-GENI networks which GENI uses • Audiences for these tools: • Experimenters who use GENI (and the staffers, instructors, and operators who help them) • Operators who run GENI infrastructure (especially when GENI runs on shared networks)

3. Agenda • GEMINI I&M project update [20 min] • Martin Swany, Indiana University • GIMI I&M project update [20 min] • Mike Zink, UMass Amherst • GMOC operational monitoring project update [20 min] • Kevin Bohan, GRNOC • Discussion: I&M/monitoring and GENI stitching [30 min] • Chaos Golubitsky, GPO

4. Agenda • GEMINI I&M project update [20 min] • Martin Swany, Indiana University • GIMI I&M project update [20 min] • Mike Zink, UMass Amherst • GMOC operational monitoring project update [20 min] • Kevin Bohan, GRNOC • Discussion: I&M/monitoring and GENI stitching [30 min] • Chaos Golubitsky, GPO

5. Agenda • GEMINI I&M project update [20 min] • Martin Swany, Indiana University • GIMI I&M project update [20 min] • Mike Zink, UMass Amherst • GMOC operational monitoring project update [20 min] • Kevin Bohan, GRNOC • Discussion: I&M/monitoring and GENI stitching [30 min] • Chaos Golubitsky, GPO

6. Agenda • GEMINI I&M project update [20 min] • Martin Swany, Indiana University • GIMI I&M project update [20 min] • Mike Zink, UMass Amherst • GMOC operational monitoring project update [20 min] • Kevin Bohan, GRNOC • Discussion: I&M/monitoring and GENI stitching [30 min] • Chaos Golubitsky, GPO

7. Discussion: I&M, Monitoring, and GENI cross-aggregate stitching Chaos Golubitsky October 23, 2012 www.geni.net

8. Motivation • GENI cross-aggregate stitching is coming soon • Limited capability available to experimenters by GEC16 • In the I&M and monitoring communities: • What tools and functionality are we building which can help stitching users? • What do we need from the stitching implementation to make our tools work?

9. Overview • Intro to GENI network stitching • Why stitching users need I&M and monitoring • Monitoring-related stitching topics This is intended as a discussion --- please interrupt!

10. Intro: What is cross-aggregate stitching? • Creation of dynamic experimental topologies containing network resources provided by more than one aggregate • Example: an experimenter reserves a slice containing: • A node at an ExoGENI rack at RENCI • A node at an InstaGENI rack in Utah • A L2 data plane link between those two nodes, which traverses the RENCI rack, NLR, Internet2, and the Utah rack • Current status: • Stitching exists within several major aggregates • Hard work has been done defining cross-AM stitching • May be usable by experimenters soon (GEC16?)

11. Why stitching users need monitoring • Experimenters need to know: • Did my reservation succeed? • What is the operational state of the links in my experiment? • Operators need to know: • What experimenters are active on my network? • What remote networks are bridged to my VLANs? • The questions aren’t new, but the answers are more complex under stitching: • The state involves more different AMs and networks • New software and APIs will introduce new problems

12. Problem: links between interfaces • GENI tools will be aware of links between resources and devices on different aggregates • Links and interfaces need to be named consistently so tools can reference them: • GENI aggregate-controlled interfaces: • The stitching API will provide names • Do we have any requirements for names so I&M and monitoring can use them? Uniqueness? Format? • Non-GENI interfaces/devices in the path: • Device operators may collect/share operational stats • Can we help share stats with GENI users in a stitching-aware way?

13. Problem: VLANs under translation • VLANs will be bridged together across networks, and have different numbers in different places • This is not new: VLANs are bridged in the mesoscale • Stitching will make translation and bridging happen dynamically • Stitching APIs should provide information to experimenters about what VLANs exist where in their slivers • Can we help provide state and topology data to operators about multi-site VLANs which touch their networks?

14. Problem: diverse resource types • Stitching will link nodes from different compute aggregate types (ProtoGENI, ORCA, PlanetLab): • Different nodes will have different OSes and environments available • Can we provide tools which give experimenters an end-to-end view of the health of their data plane networks? • Stitching will link networks with different hardware and different slicing mechanisms: • Can we help experimenters understand the network properties of their slices? • Can we help operators understand the network properties of adjacent networks?

15. Solutions: things we could do • Some improvements we think might be feasible for I&M and monitoring projects: • Implement state and measurement data for interfaces and links • Collect or import network device data from sources that make up the networks implementing stitching • Provide tools for experimenters to debug end-to-end connectivity and test network properties in their slices • UI improvements to help make sense of stitched topologies: • “UI” is used loosely here: automatically generating a table of VLANs/link names would help users who need that data

16. Your thoughts? • What are I&M and monitoring projects doing in the GEC16 timeframe that would help stitching’s alpha experimenters and operators? • What do we need stitching implementers to take into account, from an I&M and/or operations perspective, in order for our tools to work well?