2. TG09 Gateway Face to Face Please make yourself comfortable at the front of the room! Nancy Wilkins-Diehr TeraGrid Area Director for Science Gateways wilkinsn@sdsc.edu TeraGrid 09, June 24, 2009

3. First, humor me with a short game Then we’ll look at where we’ve been and where we’re going TeraGrid 09, June 24, 2009

4. Gateway Jeopardy Gateway Statistics1 Science Applications SecurityAtt-based authGateway Trivia 10 20 30 40 50 TeraGrid 09, June 24, 2009 Source: James Madison University Get me out of here

5. Which gateway used the most CPU time in 2008? SCEC, 1M hours TeraGrid 09, June 24, 2009

6. Which gateway ran the most jobs in 2008? SIDGrid, 118, 256 = 325 jobs/day TeraGrid 09, June 24, 2009

7. How many gateways did we start with and how many do we have today? 10 and 35 TeraGrid 09, June 24, 2009

8. Name 2 gateways that use Condor to submit jobs nanoHUB, TeraGrid Bioportal TeraGrid 09, June 24, 2009

9. Which site runs the most community account jobs? NCSA, 83% of all jobs in 2008 TeraGrid 09, June 24, 2009

10. Which gateway makes video available to its users for analysis? Social Informatics Data (SID) Grid TeraGrid 09, June 24, 2009

11. Which gateway’s success depended on the launch of a satellite? Asteroseismology Modeling Portal, the Kepler sattelite TeraGrid 09, June 24, 2009

12. Which gateway serves science domains from plant biology to linguistics? Geographic Information (GI) Science Gateway TeraGrid 09, June 24, 2009

13. Which gateway is accessible from igoogle? Open Life Science Gateway Log in at google.com, click add stuff, search for TeraGrid TeraGrid 09, June 24, 2009

14. Which gateway has over 600 google scholar references? Google scholar reports 601 references to the Robetta gateway, including many PubMed publications TeraGrid 09, June 24, 2009

15. What does a PI agree to on the user responsibility form? 2.2.1 Additional required information for community accounts IP address or DNS name of the portal machine Logging of requester's IP address, UTC timestamp and username on the portal Current estimated long-term disk storage requirements for the community account (this can be modified in the future to accommodate gateway growth) Paths to directories on the RP cluster where scripts and executables can be run by an un-verified user from the portal, e.g. $HOME/bin Optionally, for each script or executable in the named directory, provide Estimated maximum number of processors/nodes Estimated maximum run time Estimated short-term storage requirements per user per job TeraGrid 09, June 24, 2009

16. What does the gateway support kit include? GridShib, commsh TeraGrid 09, June 24, 2009

17. What was the summary from last year’s gateway risk analysis Most of the Gateways that answered our questionnaire seemed to be well managed and in fact cared about security issues. We were pleased to see things like patch management systems in place and checksums being used to detect code changes. We did not examine any Gateway code, but hope that the Gateways will check all user input for saneness and appropriateness. TeraGrid would like to assume that the Gateways are secure so that Gateway accounts may be treated like any other user account. TeraGrid 09, June 24, 2009

18. What PY5 activity is a direct result of the gateway security summit? Victor Hazlewood’s work to pursue standardized treatment of community accounts TeraGrid 09, June 24, 2009

19. What are two examples of observed security problems to date? Credential management, passwordless ssh TeraGrid 09, June 24, 2009

20. By what date do all gateways need to implement attribute-based authentication? September, 2009 TeraGrid 09, June 24, 2009

21. Which gateways have implemented attribute-based authentication? TeraGrid 09, June 24, 2009 gisolve, amp, and bioportal are done. nanohub, jimmy neutron, and tera3d are in progress.

22. Who was the first RP site to install the gateway support kit? NCSA TeraGrid 09, June 24, 2009

23. Besides not having Nancy bug you about user counts, name one potential benefit of attribute-based authentication TeraGrid can do per-user accounting for a gateway TeraGrid 09, June 24, 2009

24. What is the string called that identifies a gateway? entityID TeraGrid 09, June 24, 2009

25. Who makes sure gateways can use the TeraGrid in production? Who answers gateway help desk tickets? Stu Martin and Yan Liu TeraGrid 09, June 24, 2009

26. What year did the gateway program start? 2004 TeraGrid 09, June 24, 2009

27. Who can become a TeraGrid gateway? Anyone who is approved for an allocation TeraGrid 09, June 24, 2009

28. How often are update slides requested? Quarterly TeraGrid 09, June 24, 2009

29. Who did the first build-a-gateway-in-a-day tutorial? Shaowen Wang and Yan Lius TeraGrid 09, June 24, 2009

30. Five years! 84 presentations –And that’s only by me >70 gateway calls Hundreds of gateway@teragrid.org emailsgateway@teragrid.org Scores of quarterly slides 5 annual TG meetings Where did we begin? What have we achieved? Where are we going? TeraGrid 09, June 24, 2009

31. 30 Nancy’s Excellent TeraGrid Adventures

32. 31 TeraGrid 09, June 24, 2009

33. 32 RATS Requirements Analysis Teams Gathering requirements from Gateways Looking for commonalities, methodologies Determine how funded Gateway participants and TG staff can work together to accomplish goals TeraGrid 09, June 24, 2009

34. 33 Gateway RAT timeline February (1-2 week): -put together RATs team -define/refine timeline and deliverables February (2 weeks): -Review survey -send survey to gateway leaders for information collection -Review LEAD requirements (Dennis’s document) -Review user models (Von’s document) -Put together all relevant documents and articles (hotgrid,community allocation) etc -Review SGW milestones from the GIG proposal, understand them February (1-2 week) -Analyze survey -Adjust user models -Identify commonality and uncommonality -Create outline of primer -Identify possible time constraints for science gateway before AHM (test accounts) March (2 weeks) -Address possible clarification of survey answers with gateway leaders. -Contact Gateway developers to check user model -Start writing primer -if any, jump start gateways for demo scenarios. March (2 weeks) -Identify tasks/issues to be raised to specific working group -Identify GIG sgw team -finish draft of primer/requirements -Send draft to esc,security,portals,accounting,gateways wg. March (1week) -Get ready for AHM (presentation, copies, agenda) April (1 week) -Hold workshop at AHM -Present draft of SGW RAT primer -Demo -Define new timeline and deliverables TeraGrid 09, June 24, 2009

35. 34 Summarizing Gateway needs in the following areas What apps will you run Allocation model User models Cert requirements Security Accounting Status of operation, plans Critical deadlines Long term software requirements On Demand Other Leaders and technical contacts Scientific community Description URL Funding - source and personnel Middleware infrastructureWhat features do you need from TG What do you use outside of TG TeraGrid 09, June 24, 2009

36. 35 Original surveys and reports still available http://www.teragridforu m.org/mediawiki/index.p hp?title=Science_Gatew ays:_Internal http://www.teragridforu m.org/mediawiki/index.p hp?title=Science_Gatew ays:_Internal Click on Past Management TeraGrid 09, June 24, 2009

37. How far have we come? What have we done? Most importantly, what can we do better? Community accounts - established –Security policies –Improvements still needed? Community software areas – established –Any improvements needed? Gateway community - established –Recommended software –Searchable email archives –Shared experiences, model for other organizations –Improvements? Reliability, scaling –I don’t think we’re there yet, but what specifically can we do –GRAM5? TeraGrid 09, June 24, 2009

38. Allocations –Recommendations for PIs –Built support with reviewers –Still challenges? Scheduling –Metascheduling, on demand, per user limits - community account support –Still challenges Common software/services –Never really panned out Documentation –In good shape? Persistent funding for gateways TeraGrid 09, June 24, 2009

39. What are we working toward? Previously stated PY4-5 goals TeraGrid integration will be straightforward for new and existing gateway developers –Great documentation in 2008 –Current focus – streamlined community accounts There will be a set of easy to discover general services provided by and for Gateways –In progress The targeted support program will adapt to changing needs –Done We will be able to routinely count end gateway users –In progress, done by September 2009 There will be avenues for sustained Gateway funding –Some good progress TeraGrid 09, June 24, 2009

40. What am I excited about right now? Gadgets, Twitter, Yahoo YUI, interesting young people in science Gateway software advertised along with command line TG software Ability to charge user allocations for the use of gateways –Gateways as a useful tool for science! Pursuing a sustained funding program for gateways –Possibly starting with directorate workshops Quarry hosting packaged with gateway software –OGCE, SimpleGrid Attribute-based authentication Standardized community account treatment GRAM5 New groups interested in developing gateways –Center for Analytical Ultracentrifugation of Macromolecular Assemblies –J. Craig Venter Institute –Roche Pharmaceuticals Support from Vice President of engineering of the 454 Life Sciences division PY6 planning starts soon (goals, SOWs to meet those goals) TeraGrid 09, June 24, 2009