The GENI Meta-Operations Center (GMOC) If it’s research, why do we care about operations?

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

Federated Virtualized

GENI Meta-Operations Center

Operations is important Reliability Repeatability User Opt-in

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?

GMOC Architecture

GENI Meta-Operations Center

GMOC Translator - Translates information from other formats into consistent data format GMOC Repository - Central datastore for operational data from all GENI parts Operations - Watches Data to provide useful functions like Emergency Shutdown GMOC Exchanger - Polls and/or receives operational data from aggregates GENI Meta-Operations Center

GMOC Exchanger - Polls and/or receives operational data from aggregates

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

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

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

Early GMOC Functions

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

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

Emergency Stop

Challenges for GENI Operations

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)

Layers of Visibility GENI Aggregates

Layers of Visibility GENI Components

Layers of Visibility

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

Operations for Virtualized Infrastructure

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

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)?

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

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

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?