70 likes | 234 Views
PGTools Spiral 2 Year-end Project Review. University of Utah PI: John Regehr , Co-PI: Robert Ricci Staff : Leigh Stoller, Jon Duerig, Gary Wong Utah Students: Matt Strum Aug 31 , 2010. Project Summary.
E N D
PGToolsSpiral 2 Year-end Project Review University of Utah PI: John Regehr, Co-PI: Robert Ricci Staff: Leigh Stoller, Jon Duerig, Gary WongUtah Students: Matt Strum Aug31, 2010
Project Summary • This work will extend the University of Utah Emulab experiment lifecycle management software to become a “full service” front end for experiments on the ProtoGENI control framework and potentially for other frameworks based on the GENI control APIs. These tools include: • Emulab web interface and GUI • NS-like frontend language • Richer sliver configuration (IP addresses, routes, accounts, etc.) • Event system • Software installation (tarballs, RPMs, etc.) Aug31, 2010
Milestone & QSRStatus Aug31, 2010
Accomplishments 1: Advancing GENI Spiral 2 Goals • Attracting users: now linked from Emulab “Begin Experiment” page: • https://www.emulab.net/beginexp_html.php3 • Documentation and examples released • http://www.protogeni.net/trac/protogeni/wiki/CookedMode • https://users.emulab.net/trac/emulab/wiki/pgeniNodes • Many, many bugfixes and stability improvements • Stable enough to introduce to users at our GEC8 tutorial, but not yet stable enough to have 20 people creating slices all at once • Having such a rich “client” helps drive CF design Aug.31, 2010
Accomplishments 2:Other Project Accomplishments • Map-based GUI • http://www.protogeni.net/trac/protogeni/wiki/MapInterface • Partially supported by this contract, partially by NSF MRI • Uses Google Maps to provide a geographical view of nodes • Started as a simple client to show members of ProtoGENI federation • Has evolved to become a full-fledged slice creation interface – “swallowed” our earlier flash GUI • Is quite sophisticated, good for understanding how the system works • Nice point between fairly heavyweight Emulab interface and simple command-line tools Aug 31, 2010
Issues • Tool interoperability • Emulab tools assume they have complete control over slices they create • Other tools modifying slices confuses them (eg. Kentucky Instrumentation Tools) • This means they don’t play well with other tools that want to modify slices • Unclear how fixable this is: our system is very large and makes this assumption strongly • Map GUI can probably be made to play well with other tools more easily than Emulab interface Aug.31, 2010
Plans • Remainder of Spiral 2 • Finish up third version of user guide – include precise table of what’s supported and what’s not • Spiral 3 thoughts • Spend some more time thinking about tool interoperability • Examine whether our tools can be run on GENI AM API – quite possibly not, so investigate what would need to be done to AM API to support them, as a driver • More work on what happens when multiple experimenters create slices at once • Move some emphasis to map-based GUI? Aug.31, 2010