fauna
Uploaded by
6 SLIDES
194 VIEWS
60LIKES

Overview of OMF Aggregate Manager API and Experiment Control Integration

DESCRIPTION

This document outlines the functionalities of the OMF (Open Masked Framework) Aggregate Manager (AM) API, detailing its role as the intermediary between the Experiment Controller (EC) and Resource Controller (RC). It discusses aspects such as resource enrollment in experiments, service provisioning, and remote management capabilities. The document highlights the plugin architecture, multiple interfaces (XMPP, HTTP), and the ability to interact with measurement results and databases for powerful analysis and visualization. Future integration needs for control interfaces are also noted.

1 / 6

Download Presentation

Overview of OMF Aggregate Manager API and Experiment Control Integration

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. Jolyon White GEC9, 4th November 2010 OMF Aggregate Manager API

  2. OMF Entities • OMF AM != GENI AM • EC enrols resources in experiment + orchestrates experiment • AM provides services to EC (and other admin entities) EC = Experiment Controller RC = Resource Controller XMPP RC RC RC RC EC AM

  3. OMF Aggregate Manager • “Grid Services”: • CMC (remote monitoring and control) • PXE, Frisbee, Saveimage for loading & saving OS images • Inventory  database describing testbed resources • Result service  visualization of OML databases • Plugin architecture (Ruby) • Multiple interfaces: • XMPP / PubSub • integrates with EC/RC comms fabric • Discovery trival – clients don’t need to know location of service provider • HTTP – simple GET method query interface (RPC)

  4. Example – Measurement Result Interface • http://10.0.0.200:5053/result/dumpDatabase?expID=monitor2 • http://10.0.0.200:5053/result/listTables?expID=monitor2 • http://10.0.0.200:5053/result/getSchema?expID=monitor2 • Results returned as XML document, CSV, JSON etc. • Can also specify a query in the request body • XML format, similar to an SQL SELECT statement • Allows powerful analysis • Used in conjunction with visualization service (web service)

  5. Visualization

  6. OML – loose coupling • Rendez-vous on a well-known database location • OML does not have a control interface • But it will need one in the near future

More Related