1. Sponsored by the National Science Foundation GENI Experimenter Portal Service Developers Roundtable GENI Engineering Conference 16 Salt Lake City, Utah Tom Mitchell March 19, 2013 www.geni.net

2. Sponsored by the National Science Foundation2March 19, 2013 FUTURE OF GRAPHICAL RESOURCE ASSIGNMENT TOOLS

3. Sponsored by the National Science Foundation3March 19, 2013 GENI Experimenter Portal Introduction

4. Sponsored by the National Science Foundation4March 19, 2013 GENI Experimenter Portal Introduction (cont.)

5. Sponsored by the National Science Foundation5March 19, 2013 Resource Allocation Tools

6. Sponsored by the National Science Foundation6March 19, 2013 Resource Allocation Tools GENI 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. Sponsored by the National Science Foundation7March 19, 2013 Resource Allocation Tools Looking 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. Sponsored by the National Science Foundation8March 19, 2013 INTEGRATION OF PORTALS AND ALL TOOLS WITH GRAPHICAL INTERFACES

9. Sponsored by the National Science Foundation9March 19, 2013 Integration of Portals and Tools

10. Sponsored by the National Science Foundation10March 19, 2013 Tool/Portal integration GENI 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. Sponsored by the National Science Foundation11March 19, 2013 Tool/Portal integration Looking 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. Sponsored by the National Science Foundation12March 19, 2013 Tool/Portal integration Looking 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!