1 / 12

Tom Mitchell March 19, 2013 geni

GENI Experimenter Portal Service Developers Roundtable GENI Engineering Conference 16 Salt Lake City , Utah. Tom Mitchell March 19, 2013 www.geni.net. Future of graphical resource assignment tools. GENI Experimenter Portal Introduction. GENI Experimenter Portal Introduction (cont.).

lynley
Download Presentation

Tom Mitchell March 19, 2013 geni

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. GENI Experimenter PortalService Developers RoundtableGENI Engineering Conference 16Salt Lake City, Utah Tom MitchellMarch 19, 2013 www.geni.net

  2. Future of graphical resource assignment tools

  3. GENI Experimenter PortalIntroduction

  4. GENI Experimenter PortalIntroduction (cont.)

  5. Resource Allocation Tools

  6. Resource Allocation ToolsGENI Experimenter Portal • Uses GENI AM API to manage resources • Currently 7 aggregates (ExoGENI, InstaGENI, ProtoGENI) • Point-and-click web-based UI • Not particularly “graphical” or “visual” • Good introductory tool • Makes easy things easy, hard things possible • Capable of any web-based presentation • Topology visualization • RSpec construction (visual, textual) • Tool/portal integration or linking • Limited capabilites • No topology embedding; one aggregate at a time

  7. Resource Allocation ToolsLooking ahead • There is room for many resource assignment tools • They fill different niches: beginners, advanced users, scriptable, adaptive • Innovation is important • Borrow ideas from others, let experimenters vote with their feet • Standards are key • Allow access to all aggregates from all tools • Construct/embed with one tool, view/modify with another

  8. Integration of portals and all tools with graphical interfaces

  9. Integration of Portals and Tools

  10. Tool/Portal integrationGENI Experimenter Portal • The GENI Experimenter Portal currently integrates with existing tools in several ways • Embeds Flack • Download from Utah, pass in slice and user context • Provides configuration data package for omni • Acts as OpenID identity provider to Seattle • Preliminary discussions with GEMINI to support integration

  11. Tool/Portal integrationLooking Forward • Common constructs for tool interoperability • Standardize naming, semantics on UIs • Focus on inputs/outputs of the various lifecycle phases • Encourage interoperability and an open marketplace • Tools should: • Use standard and common APIs (eg. GENI AM API) • Engage in good security practices (private keys, passwords) • Hosted tools need a “speaks for” capability

  12. Tool/Portal integrationLooking Forward (cont.) • Pushing towards a seamless user experience while providing choice and an open marketplace • Tools will need more standard APIs (SA, MA/IdP) • Tools should choose an appropriate authentication model (certificates, OpenID) • Link to online tools, embed online apps, integrate with desktop tools • Consume and produce standard artifacts (RSpec) • Documentation!

More Related