1 / 42

Building Science Gateways

zlhna
Download Presentation

Building Science Gateways

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. Building Science Gateways Marlon Pierce Community Grids Laboratory Indiana University

    2. What Is a Web Portal? Web container that aggregates content from multiple sources into a single display. “Start Pages” Typically consume RSS/Atom news feeds. More powerful versions these days support Flickr, calendars, games, etc. Gadgets, widgets Examples: iGoogle, Netvibes, My Yahoo!

    3. Grid Computing Overview Grid computing software is designed to integrate large supercomputing facilities. TeraGrid, Open Science Grid, EGEE, etc. This is done via network services Key Service Components Authentication and authorization framework (MyProxy) Remote process access and control (GRAM, Condor) Remote file, I/O access (GridFTP) Additional Services Information services, replica management, database federation, storage management, schedulers, etc. Example Grid Software Stacks: CTSS and VDT

    5. Science Portals and Gateways Science Gateways adapt Web portal technology to build user interfaces to the Grid. Science portals resemble standard portals, but must also Support access to computing and storage resources. Allow users remote, Unix-like access to these resources. Provide access to science applications and data sets. And we must provide value added services as well as user interfaces.

    7. Terminology Portlet: this is a standard Java component that generates HTML and can also act as a client to a remote service. Lives in a portal container. I will also use this term generically. Web Service: a remotely invokeable function on the Internet. SOAP: the XML message envelop for carrying commands over HTTP. WSDL: describes the service’s API in XML. REST: A variation of this approach. Lots more info: http://grids.ucs.indiana.edu/ptliupages/presentations/I590WebService.ppt

    8. But Why? Three-tiered Service Oriented Architecture is the network equivalent of the the famous Model-View-Controller design pattern. View: the user interface components. Controller: Web service middleware Model: the backend resources. Independence of tiers gives flexibility Services can be reused with alternative user interfaces Workflow composers like Taverna User interfaces can work with different service implementations. Drawback: reliability and robustness are issues.

    9. Two Approaches to the Middle Tier

    12. What’s In the Screenshots? GeoFEST and Disloc Portlets Live on gf7.ucs.indiana.edu Manage the user’s display: Web forms, links to output, graphics. Save user session state persistently. QuakeTables Fault DB Web Service Lives on gf2.ucs.indiana.edu Contains geometric fault models. GeoFEST and Disloc Execution Web Services Lives on gf19.ucs.indiana.edu Generates input files from fault models. Runs and manages codes.

    13. Best Practice for Scientific Web Services There are many tools to choose from. .NET, Apache Axis, Sun WS, Ruby on Rails, etc. Make them self-contained. If possible, generate input files within the service. Or have an input file generating service. Remember that they may be used by other people with other client tools. Communicate data files with URLs. Be very careful about exposing the state of the service. Don’t assume persistent connections.

    14. Components for Portals Open Grid Computing Environments Examples. See http://www.collab-ogce.org/

    15. Components for Science Portals OGCE is founded on the principal that portals should be built out of reusable parts. Key standard in our first phase: the JSR 168 portlet specification. Portlets can run in multiple containers uPortal, Sakai, GridSphere, LifeRay, etc. Allows us to build Grid specific components and deploy along side other goodies: Sakai collaboration tools, contributed portlets, etc. Future: Open Social compliant Google Gadgets

    20. Dashboard Portlet

    24. Condor and Condor-G

    26. Client Libraries for Grid Computing

    27. Two Major Grid Client Efforts The Java COG Kit Supports several versions of Globus and SSH. Condor-G Has a Web Service interface (BirdBath) and Java client libraries. Supports Globus (v2 and v4) and several other Grid middleware systems. You can build either portlets or Web services with either of these. OGCE portlets use primarily COG We prefer Condor-G based Web services for long running jobs.

    28. CoG Abstraction Layers

    30. Coupling CoG Tasks The COG abstractions also simplify creating coupled tasks. Tasks can be assembled into task graphs with dependencies. “Do Task B after successful Task A” Graphs can be nested.

    31. Problems with Grid Client Development Grid portlets typically wrap each single Grid capability in a separate portlet Problem is that Grid portlets need to combine these operations Portlets are entire web applications, so we need a component model for portlets: reusable portlet parts Even with the COG Abstraction Layer, we must still do a lot of coding to build new applications. To address these problems we have adopted Java Server Faces Provides several nice Model-View-Controller features JSF provides an extensible framework (tag libraries) for making reusable components. Apache JSF portlet bridge allows you to convert standalone JSF applications (development phase) into portlets (deployment phase).

    32. GTLAB Example <html> <body> <f:form> <o:submit id=”test” action=”next_page” /> <o:myproxy id=”pr” hostname=”gf1.ucs.indiana.edu” port=”7512” lifetime=”2” username=“mnacar” password=”***” /> <o:jobsubmit id=”task” hostname=”cobalt.ncsa.teragrid.org” provider=”GT4” executable=”/bin/ls” stdout=”tmp/result stderr=”tmp/error” /> </o:submit> </f:form> </body> </html>

    34. Managing Scientific Workflows

    35. Scientific Workflows Portal interfaces encode scientific use cases. If you have a rich set of services, it is a lot of work to make portlets for all possible use cases. And power users will have always want something more. Example: our CICC project has dozens of chemical informatics Web services. http://www.chembiogrid.org.wiki Workflow composers can simplify this. Allow users to encode and execute their own use cases.

    36. Web Services and Workflows Perform a similarity search on the NIH DTP Human Tumor data. Filter the results based on Pharmacokinetic properties (FILTER) Convert to 3D (OMEGA) Docking into a pre-defined protein (FRED) Visualize (JMOL).

    37. OGCE’s XBaya Workflow Composer

    38. Future of Science Gateways

    42. More Information Contact me: mpierce@cs.indiana.edu See what I’m up to: http://communitygrids.blogspot.com/ OGCE software: http://collab-ogce.org/ QuakeSim: http://www.quakesim.org/ CICC: http://www.chembiogrid.org/wiki/ Lots of people worked on all of these.

More Related