grid portals a user s gateway to the grid n.
Skip this Video
Loading SlideShow in 5 Seconds..
Grid Portals – A User’s Gateway to the Grid PowerPoint Presentation
Download Presentation
Grid Portals – A User’s Gateway to the Grid

Grid Portals – A User’s Gateway to the Grid

177 Vues Download Presentation
Télécharger la présentation

Grid Portals – A User’s Gateway to the Grid

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Grid Portals –A User’s Gateway to the Grid Dennis Gannon, Indiana University Geoffrey Fox, Indiana University Beth Plale, Indiana University Marlon Pierce, Indiana University Mary Thomas, Univ. of Texas Charles Severance, Unversity of Michigan Gregor von Lazewski, Argonne National Labs Jay Alameda, NCSA Grid Summer School: Grid Portals

  2. Other Important Contributors • People who do the “Real” work. • Argonne: Micheal Hategan, Kaizar Amin, Shashank Shankar • Indiana Grids Lab:Shrideep Pallickara, Ali Kaplan, Ahmet Topcu, Ahmet Sayar, Fatih Mustacoglu • Indiana CS: Octav Chipara, Marc Christie, Liang Fang, Matthew Farrellee, Gopi Kandaswamy, Deepti Kodeboyina, Wei Lu, Sriram Krishnan, Yogesh Simmhan, Alek Slominski, Anuraag Sarangi • University of Texas: Maytal Dahan,Tomislav Urban, Eric Roberts, Akhil Seth • University of Michigan:Joseph Hardin, Glenn Golden, Jim Eng • NCSA: Shawn Hampton, Al Rossi, Greg Daues Grid Summer School: Grid Portals

  3. Outline • Hour 1 – An overview of Grid Portals • The Big Picture • Example Applications • Hour 2 – The standard Architecture • Portal servers and portlets • Hour 3 – Working with Standard Grid Tools • MyProxy Server and Gram Job Submission • Web and Grid Services • Hour 4 – Advanced topics Grid Summer School: Grid Portals

  4. Grid Application Factory Service Application Factory Grid Portals App Instance App Instance App Instance Resource layer 1000s of PCs ->massive supercomputers The Big Picture Launch, configure And control Open Grid Service Architecture Layer Data Management Service Registries and Name binding Security Policy Logging Accounting Service Administration & Monitoring Reservations And Scheduling Grid Orchestration Event/Mesg Service Open Grid Service Infrastructure (web service component model) Online instruments Grid Summer School: Grid Portals

  5. Event and logging Services The User Application Factory Services Messaging and group collaboration Portal Server Directory & index Services User's Persistent Context MyProxy Server Metadata Directory Service(s) The Big Picture • The Grid is defined by a collection of distributed Services • For most users the primary interaction with the Grid will be through a portal Grid Summer School: Grid Portals

  6. What do users want from a portal • Access to grid services • Security services • Management of my grid certificates • VO management (who is in my group?) • Remote File management • Access to file and metadata directories • Staging files and moving them • Remote Job management • Simple remote job submission and monitoring • Complex workflow management • Access to information services • Directories, index tools, messaging, notification • Application interfaces • Hiding the details of Grid middleware • Access to collaboration • Shared video and applications Grid Summer School: Grid Portals

  7. Some Examples • Grappa • High Energy Physics (Indiana & Chicago) • Gateway Computational Sciences Portal • Earthquake Science (Indiana) • Nees Grid • Earthquake Engineering (Michigan) • Alliance Portal • NCSA toolkit (Indiana,NCSA, Argonne) • Open Grid Computing Environment (OGCE) Portal • Part of NSF Middleware Initiative: a standard toolkit of portal tools. • Indiana, Micigan, Texas, NCSA collaboration Grid Summer School: Grid Portals

  8. Grappa This is a scientific notebook example there is text and there is also some interesting graphics and some scripts GRAPPA – A Science Portal • Atlas Experiment • Large Hadron Collider • 100 MB/sec (10PB/year) • Grid Access Portal for Physics Apps • To provide Atlas physicists with an point of access to Grid resources • Manage submission of Athena and AtlSim jobs to condor cluster • Manage interaction of analysis with physics data and grid services Grappa Notebook App Manager Mesg servc events Job op servc Analysis module detector Particle prop histogram Grid Summer School: Grid Portals

  9. NEES – • George E. Brown, Jr. Network for Earthquake Engineering Simulation • Large Installations of physical equipment for earthquake experiments and simulations • Part of the award is to make equipment available for remote collaborators • Focus is on collaboration and experimental equipment sharing in addition to access to computation Grid Summer School: Grid Portals

  10. NEESGrid System Integration Team • Developing infrastructure to: • access collaborative tools for experiment planning, execution, analysis, and publication. • perform tele-observation and tele-operation of experiments; • publish to and make use of a curated data repository using standardized markup; • access computational resources and open-source analytical tools; • NCSA, ANL, USC/ISI, UMich, USC Grid Summer School: Grid Portals

  11. NEESGrid Components Grid Summer School: Grid Portals

  12. NEESGrid Examples Grid Summer School: Grid Portals

  13. Based on CHEFCompreHensive CollaborativEFramework • Based on Jakarta Jetspeed – Portal Toolkit • Portal provided custom personal start pages for individuals • Unit of extensibility: Portlet • CHEF – Portal-based Collaborative Application Framework • Adds notion of groups of users • Adds notion that groups have customizable portals (i.e. group portal administrator) • “Services Soup” – CHEF, OKI, COG, OGSA … • Unit of extensibility: Module (Portlet, Teamlet, Service) Grid Summer School: Grid Portals

  14. CHEF: Initial Applications • Common Group-Aware Tools • Announcements, chat, calendar, threaded discussion, resource repository, webdav • Learning Management System • Assignment tool, quizzing tool, OKI support • Grid Infrastructure • Grid portal toolkit – used in NEESGrid • More Later! Grid Summer School: Grid Portals

  15. ServoGrid: Web Services and Portlets for Earthquake Science Using Web Services and portlets to support earthquake simulation and forecasting. Grid Summer School: Grid Portals

  16. Solid Earth Research Virtual Observatory Grid • A number of simulation methods for studying earthquakes are being developed by the ServoGrid team including: • Disloc (JPL): Calculates surface displacements for model faults in an elastic half-space. • Simplex(JPL): Inverts Disloc to calculate model fault parameters from given surface displacements (GPS data) • GeoFEST: 3D finite element code for calculating nodal displacements and tractions using realistic fault models. • Virtual California (UC-Davis): Simulates interactions between fault segments. Models time evolution of fault friction buildup and release on known California fault segments. • PARK (Brown): A boundary element program to calculate fault slip velocity history. Grid Summer School: Grid Portals

  17. Interoperability through Data Sharing Grid Summer School: Grid Portals

  18. What the Previous Slide Means • SERVOGrid codes need to interoperate through shared data. • EX: Simplex surface observation points may be used as input to Disloc. • “What if I had more observations stations or another satellite? Would it decrease model uncertainties?” • EX: Simplex can be used to create model faults need by Virtual California and Simplex. • “Would my model be better if I had two fault segments?” • Data sharing may be either • Synchronous: link inputs and outputs • Asynchronous: store simulation results in databases with real observations. Grid Summer School: Grid Portals

  19. GeoFEST Simulation of 1994 Northridge Earthquake Grid Summer School: Grid Portals

  20. ServoGrid: Portal Access to Codes • Codes are written independently, will need to run on workstations, clusters, and NASA supercomputers. • As codes become more robust and accepted, problems emerge: • Need to manage information about distributed data sources: multiple databases, sensors, simulated data. • Need to organize, manage information about multiple code installation sites. • Need to simplify access to data, use of codes, and use of visualization/analysis tools for broad range of users • Need to link together Grid Summer School: Grid Portals

  21. SERVOGrid: Accessing Data • Codes also need access to a variety of data, including • Synthetic data generated by other codes • Historical fault and earth mantle data obtained from journals and other references • Web accessible GPS and Seismicity data. • So in addition to application services, we need data services Grid Summer School: Grid Portals

  22. RepositoriesFederated Databases Sensor Nets Streaming Data Database Database Analysis and Visualization Loosely Coupled Filters Closely Coupled Compute Nodes SERVOGrid Architecture Grid Summer School: Grid Portals

  23. SERVOGrid Services • We have developed a number of core services to support • Access to codes through browser interfaces • Bind services to data sources • Link several dependent services into a single service • Site Dependent Services • Job Submission • File Transfer • Job Monitoring • Host Monitoring • Visualization services Grid Summer School: Grid Portals

  24. More ServoGrid Services • Site Independent Services • Context Management for metadata • Batch Generation • Session archiving Services • Data services to access Fault data. • Coupling services • We use Apache Ant as a web service to link several dependent tasks (such as steps needed to run visualization). • Ant tasks themselves may be Web service clients • More on this later Grid Summer School: Grid Portals

  25. Computing Portal Grid Web Services • We have built a suite of general purpose Grid Web services for managing distributed applications. • Core Computing services define general purpose functions: • Ex: job submission, file transfer, job monitoring, management of jobs and results • Described as a GridShell as plays same role to Grid that Shell does for UNIX on a single machine • Application Grid Web services include metadata about applications. • Built on top of core services. • Original application NOT changed • We have developed a toolkit that allows one to convert general software packages into Grid Web Services and manage application collections Grid Summer School: Grid Portals

  26. Application Grid Web Services • AGWS are designed to make scientific applications (i.e. earthquake modeling codes) into Grid Resources • AGWS services are described by two XML Schemas: • Abstract descriptors describe application options. Used by the application developer to deploy his/her service into the portal. • Instance descriptors describe particular user choices and archive them for later browsing and resubmission. Grid Summer School: Grid Portals

  27. SERVOGrid Portlets and Portal Stacks • User interfaces to SERVOGrid services (Code Submission, Job Monitoring, File Management for Host X) are all managed asportlets. • Users, administrators can customize their portal interfaces to just precisely the services they want. Aggregation Portals User facing Web Service Portals Message Security, Information Services Application Grid Web Services Core Grid Services Grid Summer School: Grid Portals

  28. SERVOGrid Portal • SERVOGrid codes, data, and services are managed on a testbed of IU, USC, and JPL resources. • Hosts include danube, noahsark, solar, grids • We provide access to these with a Jetspeed-based portal. • Portlet components are Web service clients to remote services • Portlets can also be easily shared with other portals, like the Alliance Portal Grid Summer School: Grid Portals

  29. Testbed hosts assigned to separate tabs Grid Summer School: Grid Portals

  30. Example: Host Solar Grid Summer School: Grid Portals

  31. File Selector Screenshot • Users can view files on remote hosts • Shown is user file list for host noahsark. • Host solar is also shown. • Files can be uploaded or downloaded between PC and remote host. • Files may be crossloaded between two remote hosts. • Same interface definition may be used to access databases. Grid Summer School: Grid Portals

  32. File management Tabs indicate available portlet interfaces. Lists user files on selected host, noahsark. File operations include Upload, download, Copy, rename, crossload Grid Summer School: Grid Portals

  33. Application Selection Screen Shots • Users can select from available codes • Simplex, Disloc, various VirtualCalifornia • Users also select from available hosts for particular code • grids, noahsark, solar shown • Selecting solar (Sun 64 Node E10000) prompts user for information needed to use PBS script generating service. Grid Summer School: Grid Portals

  34. User Application Selection and Submission Generate script for job submission Select desired application and host Grid Summer School: Grid Portals

  35. Application Administrator Interfaces • Application Administrators deploy and manage applications • Update screen shows various application and host parameters that are set by the user. • These are used to generate user interfaces for the selected codes. Grid Summer School: Grid Portals

  36. Administer Grid Portal Provide information about application and host parameters Select application to edit Grid Summer School: Grid Portals

  37. Context Management • Common problem of portals is to store all of the metadata associated with user sessions. • Context Management service provides simplest possible data model • Context manager provides an easy interface to data trees. • Context data nodes are defined by recursive schema that hold optional, unbounded name/value pairs and child nodes. • We use CM to store locations of job scripts, miscellaneous file URIs, etc. • CM metadata stored on file systems, XML-native databases, …. • Actual data may be anywhere. • Searched with XPath queries. Grid Summer School: Grid Portals

  38. Application Codes as Web Services • Scientific applications consist of several core Web services. • Get files to right place, script submission instructions, submit the job, get notified at various states. • We need a meaningful metadata model for applications • Describe application-specific requirements • Describe bindings of applications to host environments and to Web services Grid Summer School: Grid Portals

  39. Data Sharing Services • Codes have many common data types: • Faults • Mantle layers • Surface observation points • But they all express these differently (custom/legacy formats). • We have defined XML common data formats for these. • Services need translators to convert between legacy and common formats. • We’ve built these for Simplex, Disloc • Currently converting schemas to Geography Markup Language (GML) vast superset of what we need. • Schemas available from Grid Summer School: Grid Portals

  40. User selects codes, resources, and code data. Browser Interface User requests translated to XML data formats using the remote service. HTTP User Interface Server SOAP/HTTP Disloc Data Service Disloc Execution Service Input data exported to legacy format and transferred to execution host. Legacy output transferred back to data service and imported back into XML formats. Grid Summer School: Grid Portals

  41. The Alliance Grid Portal • Provides Portlets for • Management of user proxy certificates • Remote file Management via Grid FTP • News/Message systems • for collaborations • Grid Event/Logging service • Access to OGSA services • Access to directory services • Specialized Application Factory access • Distributed applications • Workflow • Access to Metadata Index tools • User searchable index Grid Summer School: Grid Portals

  42. Open Grid Computing Environment Portal Project • A collaboration of portal design groups to build a common set of tools for building Grid portals. • Indiana, NCSA, Michigan, Texas • Funded by • NSF New Middleware Initiative • NCSA, NPACI, DOE, NASA • Based on • Jetspeed and Chef • OGSI/OGSA • Evaluating GridShpere Grid Summer School: Grid Portals

  43. Portal Interaction Model • How should the user interact with the Grid using the portal? • Logging onto the portal should bring up you current “Grid Context” • The set of tools (portlets) you use to access remote services • Configured into groups you access from tabbed panes the way you want them and the way you last left them. • Log files of events and annotations that for a persistent record of your grid transactions • Access to your group identity within a collaboration to give you access to group news and communications Grid Summer School: Grid Portals

  44. OGCE based on a Portlet Model • A Portlet is a portal server component that provides a basic functionality rendered in a user configurable window in a portal pane. Event and logging Services The User Application Factory Services Portal Server Messaging and group collaboration Portlet 1 Portlet 2 Portlet 3 Portlet 4 Portlet 5 Portlet 6 Directory & index Services User's Persistent Context MyProxy Server Metadata Directory Service(s) Grid Summer School: Grid Portals

  45. Advantage of portlet architecture • Each Grid service can be associated with a unique portlet • Very easy to add new services • Many different Groups can contributed portlets which can be plugged into a portal. • Currently Indiana, Argonne, Michigan, NCSA,Texas + GridSphere portal group following this model. • Jetspeed is Apache standard. Also basis for IBM websphere portal and others. Now moving to Java Standard • Each user can select and configure the portlets he/she wishes to use • Selection becomes part of the persistent context Grid Summer School: Grid Portals

  46. The Hard Questions • If the Grid consists of thousands of services, do we need a portlet for each one? • Clearly not. Who will write/use all those portlets? • Is there a set of “generic portlets” that can adapt to any Grid/Web service? • Most Grid/Web services are designed to be invoked by other services… not humans • What is the right model for the user interaction? • Should some services be our “agent services” that talk to us while managing our interaction with remote services? • If a service wants to interact with a human, should it not supply its own “portlet”? Grid Summer School: Grid Portals

  47. Hour 2. Portal Programming The basic architecture How to write a portlet Grid Summer School: Grid Portals

  48. Standard Portal Architecture • User access: • A standard browser • User provides login id & password • Portal engine • Retrieves user context from DB • User’s configuration of the portal interface and other persistent data. Standard web server Portal engine User context database Grid Summer School: Grid Portals

  49. Portlet1 Portlet2 Portlet3 Portlet4 The “Standard” Implementation • Based on the Java “Portlet” model. • IBM Websphere, Oracle, HP, Sun, BEA Weblogic, … • Open Source: • Apache Jakarta Jetspeed, Chef, Gridsphere, JPortlet … • User’s View of the portal: • A user configurable set of “panes” each containing a set of small web applications called portlets. Top view Pane 4 Pane 1 Pane 2 Pane 3 portlet5 Portlet6 Portlet7 Portlet8 Portlet9 Portlet10 Grid Summer School: Grid Portals

  50. A Look at a pane and portlet The current Visible pane Proxy Manager Portlet Grid Summer School: Grid Portals