1 / 25

Maximizing GENI Operations Efficiency: GMOC Meta-Operations Center

Learn about the GENI Meta-Operations Center's role in coordinating and managing operational tasks to ensure the smooth functioning of GENI projects. Explore the challenges and functions of GMOC in GENI's ecosystem.

teleri
Download Presentation

Maximizing GENI Operations Efficiency: GMOC Meta-Operations Center

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 • Project to Build • Infrastructure to support greenfield network science • NOT Research in itself • The Test Track, not the car

  3. GENI Summary • Funded by NSF • BBN Technologies serves as the GENI Project Office (GPO) • 2 Solicitations so far • Solicitation #1 had 29 funded projects • Solicitation #2 had 33 funded projects

  4. GENI Control Frameworks • GPO grouped projects into control framework clusters • each cluster is anchored by a project to develop a control plane for the facility • 5 clusters initially: • PlanetLab • TIED • ProtoGENI • ORCA/BEN • ORBIT

  5. GENI Early Focus: “Slicing” • In GENI, a slice means a set of virtualized resources connected together to provide a single virtual testbed for a scientist • “slicing” across parts of a control framework cluster is main thrust now • future will mean inter-cluster slicing & federation with other facilities & networks

  6. GENI Meta-Operations Center

  7. What’s “Meta” mean? • GENI is made up of many loosely affiliated projects • Many projects have existing means to provide operations • But what about operating GENI as a whole? What’s needed? • Option 1/NOTHING - each part can operate independently without additional effort for GENI as a whole • Option 2/Central GENI Operations Center - all GENI resources should be centrally managed & operated by a GENI operations center • Option 3/Meta-operations - GENI projects can best handle most operational tasks. For GENI as a whole, someone should coordinate operations across projects to present a single interface to operators and users.

  8. Project C Project D Project B Project A Option 1 - Completely Distributed Cluster 2

  9. Project C Project D Project B Project A Option 2 - Centralized Cluster 1 Cluster 2

  10. Project C Project D Project B Project A Option 3 - Meta-Operations Cluster 1 Cluster 2

  11. GMOC Architecture

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

  13. Early GMOC Functions

  14. GENI View of Operational Status • Give GENI-wide view of operational status • maps & graphs • prototype other views, such as slice-by-slice views • Give Scientists access to their data • “What was going on during these 2 weeks I ran my test?”

  15. Emergency Stop Emergency Stop • Identify & Shut down Misbehaving Slices • Protect Other Slices • Ensure Stability • in Phase1, Emergency Stop will consist of a process for manual contact of projects • Emergency Stop Demonstration To be performed in 2010

  16. Challenges for GENI Operations

  17. Challenge #1: Federation • GENI has many projects • doing different kinds of things • with different abilities to provide operational data • with different requirements for 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 Challenge #2: Layers of Visibility

  19. GENI Components Challenge #2: Layers of Visibility

  20. Challenge #2: Layers of Visibility

  21. Challenge #3: Virtualized Operations • Everything is more temporary • what “slices” are out there (NOW, 3 weeks ago)? • How do we correlate current slices to future slices for repeatability • Everything is more complex • Many different groups to serve: Operators, Researchers, “Opt-in” Users • 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)?

  22. Challenge #3: Virtualized Operations • Everything is more temporary • what “slices” are out there (NOW, 3 weeks ago)? • How do we correlate current slices to future slices for repeatability • Everything is more complex • Many different groups to serve: Operators, Researchers, “Opt-in” Users • 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)?

  23. Solicitation 2: K-GENI ETRI/KISTI-GENI Collaboration • Scope: • Investigate international operational sharing and federation strategies • Look into interoperability between GMOC and dvNOC • for example: should GMOC conform to dvNOC data formats? vice versa? maybe a international “broker” to translate between them?

  24. Does GENI have any relation to “normal” networks?

  25. GMOC PI: Jon-Paul Herron jpherron@indiana.edu GMOC Team: gmoc@grnoc.iu.edu GMOC Website: http://gmoc.grnoc.iu.edu/

More Related