1 / 12

Computational Grid Portals

Computational Grid Portals. Marlon Pierce Community Grids Lab Indiana University. Open Grid Computing Environment Collaboratory. Funded by NSF’s National Middleware Initiative University of Chicago Gregor von Laszewski University of Illinois/NCSA Jay Alameda Joe Futrelle

noe
Download Presentation

Computational Grid Portals

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. Computational Grid Portals Marlon Pierce Community Grids Lab Indiana University

  2. Open Grid Computing Environment Collaboratory • Funded by NSF’s National Middleware Initiative • University of Chicago • Gregor von Laszewski • University of Illinois/NCSA • Jay Alameda • Joe Futrelle • Indiana University/Community Grids Lab and CS • Marlon Pierce • Geoffrey Fox • Dennis Gannon • Beth Plale • University of Michigan • Charles Severance • Joseph Hardin • University of Texas/TACC • Mary Thomas • Jay Boisseau

  3. What Are Grid Portals? • Computing portals provide ubiquitous, browser-based access to grid resources. • No special client software or platform needed • Access information in visually intuitive form • Provide services to support user interactions • Job archivingportal metadata management services • Combine core grid services into custom services • Launch multistage jobs with dependencies • Couple execution, file transfer, visualization/analysis • Many, many such projects • Concurrency and Computation: Practice and Experience’s special issue described more than two dozen in 2001. • GCE Research Group of the GGF is the community forum. • Thomas, Gannon, and Fox are chairs.

  4. What Are the Problems? • Problems are always the same: • How do we share portal services? • How do we reuse components between projects and groups? • Can we provide a standard abstraction for portal services and interfaces? • Can we provide an architecture that allows services and user interface components to be added in a standard way? • Need to shorten the “standard service” deployment phase so that we can concentrate on harder problems, specific sophisticated services • Fusion Grid needs very interactive, visual interface for setting up problems • Need to be able to deploy standard components like MyProxy, GridFTP, etc interfaces quickly

  5. General Portal Architectures

  6. Portal Service ComponentsSciDAC Fusion Grid Example Portlet Container SRB Client Portal Login Proxy Manager TRANSP Submit File Manager LDAP Browser GPIR IDL Clients WSDL GridPort Java COG WSDL COG/GP Java COG WSDL WSDL WSDL WSDL WSDL SRB Grid Auth GRAM Grid FTP GRIS/ GIIS GPIR IDL Services … MDSPlus TRANSP … FG Applications FG Hardware

  7. SERVOGrid Codes, Relationships Elastic Dislocation Inversion Viscoelastic FEM Viscoelastic Layered BEM Elastic Dislocation Pattern Recognizers Fault Model BEM

  8. Problems: Data Access and Sharing, Code Integration • Codes all use custom text formats for describing input and output. • Input and output data often combined with code-specific information. • Number of iterations, array sizes, etc. • Data files often created by hand from journals, online repositories • Online repositories themselves use differing formats • Challenges are to develop common data formats, access services, and client query tools.

  9. Browser Interface JSP + Client Stubs DB Service 1 Job Sub/Mon And File Services Viz Service JDBC DB Operating and Queuing Systems RIVA Host 1 Host 2 Host 3

  10. Web Services for Data Access and Computing Service Invocation • Service-oriented architecture • Web services: • WSDL: Interface definition language, describes your service • “GeoFEST may be invoked with these input types” • SOAP: Transport envelope for remote procedure calls/messages • “Invoke GeoFEST with this set of input” • Together, WSDL and SOAP are useful for manipulating, returning XML data values • WSDL and SOAP are platform independent • C/C++, Java, Python, Perl bindings. • So you can build a variety of clients that use the same backend services • Browsers and more sophisticated workbench GUIs. • Turn the problem on its head: embed service calls in legacy code • Better data access methods • I want to use your mesh generator

  11. GML Schemas as Data Models for Services • Fault and GPS Schemas are based on GML-Feature object. • Seismicity Schema is based on GML-Observation object. • Working schema available from http://grids.ucs.indiana.edu/~gaydin/schemas/

  12. Grid Testbed for Portal Demo • complexity.ucs.indiana.edu • Solaris Sunfire web server • Web server for portal • Danube.ucs.indiana.edu • Duel processor linux server • Runs AKRIA,GeoFEST, GMT • Grids.ucs.indiana.edu: • Sun Ultra 60 • Runs Disloc • Infogroup.usc.edu • Linux box • Runs Mysql fault database • Jabba.jpl.nasa.gov: • SGI Origin(?) • Runs RIVA for movies

More Related