1 / 28

GENI Meta-Operations Center: Enabling Reliable and Repeatable Network Research Operations

This article explores the pivotal role of the GENI Meta-Operations Center (GMOC) in ensuring reliability, repeatability, and user opt-in for network research operations within the GENI framework. It delves into the GMOC architecture, functions, challenges, and its importance in the context of virtualized networks and operations. The text discusses the need for collaboration among GENI participants, balancing central visibility with decentralized autonomy, and the evolving landscape of network operations in a virtualized environment. It also addresses key operational questions and highlights the gradual progress toward comprehensive solutions.

wedwards
Download Presentation

GENI Meta-Operations Center: Enabling Reliable and Repeatable Network Research Operations

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. The GENI Meta-Operations Center (GMOC) • If it’s research, why do we care about operations?

  2. GENI • Proving Ground for Network Research • NOT Research in itself • The track, not the car

  3. GENI • Federated • Virtualized

  4. GENI Meta-Operations Center

  5. GENI Meta-Operations Center • Operations is important • Reliability • Repeatability • User Opt-in

  6. GENI Meta-Operations Center • How to start - What’s the first set of things we need for GENI operations? • Step 1: what kinds of data do we need to get? • Step 2: how should that data be shared? • Step 3: what should we do with the data once we get it?

  7. GMOC Architecture

  8. GENI Meta-Operations Center

  9. GMOC Exchanger - Polls and/or receives operational data from aggregates GENI Meta-Operations Center

  10. GMOC Translator - Translates information from other formats into consistent data format GENI Meta-Operations Center

  11. GMOC Repository - Central datastore for operational data from all GENI parts GENI Meta-Operations Center

  12. Operations - Watches Data to provide useful functions like Emergency Shutdown GENI Meta-Operations Center

  13. Early GMOC Functions

  14. GENI Portal • Give GENI-wide view of operational status • In the future, provide other views, such as slice-by-slice

  15. Emergency Stop • Identify & Shut down Misbehaving Slices • Protect Other Slices • Ensure Stability

  16. Challenges for GENI Operations

  17. The Federation Challenge • GENI will have many participants • Each will be doing different things • Each will have different abilities to provide operational data • Each will have different requirements to receive operational data • GMOC depends on cooperation from them all • Balance between central visibility and decentralized autonomy will need to evolve (and continue evolving)

  18. GENI Aggregates Layers of Visibility

  19. GENI Components Layers of Visibility

  20. Layers of Visibility

  21. Layers of Visibility • How do we look at Operations? • Aggregate view • Component view • Slice view • Sliver view • What’s most likely? Some of each.

  22. Operations for Virtualized Infrastructure

  23. Virtualized Networks, so Virtualized Operations? • Everything is more temporary • How does an operations center know what “slices” are out there (NOW)? • How do we communicate to the right people? • How do we correlate current slices to future slices for repeatability

  24. Virtualized Networks, so Virtualized Operations? • Everything is more concurrent • How do researchers setting up “slices” know the state of them(and not everything else)? • How do we “shut down” the problem parts (and not everything else)?

  25. Virtualized Networks, so Virtualized Operations? • Everything is more complex • Who are the people served? • Aggregate operators & clearinghouses • Researchers • “Opt-in” users

  26. That’s a lot of questions... • ...And the answers aren’t there yet • Baby steps • Start with the most crucial issues that can be answered now • Build on the best solutions • evolve the ones that should be changed • Abandon the rest

  27. Does GENI have any relation to “normal” networks? • Federation • think: end-to-end monitoring & performance • multiple-domain information sharing • Virtualization • think: Dynamic Circuits • What’s up right now? How do you monitor it?

More Related