1 / 15

Some comments on Portals and Grid Computing Environments

Some comments on Portals and Grid Computing Environments. PTLIU Laboratory for Community Grids Geoffrey Fox, Marlon Pierce Computer Science, Informatics, Physics Indiana University, Bloomington IN 47404 http://grids.ucs.indiana.edu/ptliupages. Background Information.

cassady-roy
Download Presentation

Some comments on Portals and Grid Computing Environments

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. Some comments on Portals and Grid Computing Environments PTLIU Laboratory for Community Grids Geoffrey Fox, Marlon Pierce Computer Science, Informatics, Physics Indiana University, Bloomington IN 47404 http://grids.ucs.indiana.edu/ptliupages

  2. Background Information • Co-chair of Grid Computing Environments research group • Part of GlueX experiment at Jefferson Laboratory designing partial wave analysis portals (pretty complex interactive application) • Built/building portals for DoD High Performance Computing Office and NASA Earth Science (JPL) • Part of NCSA portal supporting chemical engineering, meteorology, astronomy • Illustrates integration of portal services and user interfaces from multiple groups • Starting DoE portal project working with Fusion application

  3. Areas of Possible Interest • Framework to build portals (roughly same as Grid Computing Environments) • Tools to construct “Application Web Services” • “Workflow” tools and standards like BPEL4WS • Re-use of existing portal services • Using a “Grid shell” model to describe core services • Experience using aggregation portals – Jetspeed • Component model for user interfaces • WSRP/WSIA Web Services for Remote Portals/Interactive Applications • Always trying to maximize re-use and use of distributed development ……..

  4. Application Metadata Actual Application Database UserServices Aggregation Portal GridComputingEnvironments Portal Services PortalServices Application Service Application Service OGSA (OGSI) Interfaces “Core”Grid SystemServices SystemServices SystemServices Raw (HPC) Resources

  5. WSDL W S Application orContent source R P Web Service Web Services as a Portlet Application as a WSGeneral Application PortsInterface with other WebServices • EachWeb Service naturally has a user interface specified as “just another port” • Customizable for universal access • This gives each Web Service a Portlet view specified (in XML as always) by WSRP (Web services for Remote Portals) • So component model for resources “automatically” gives a component model for user interfaces • When you build your application, you define portletat same time User Face ofWeb ServiceWSRP Ports define WS as a Portlet Web Services have other ports (Grid Service) to be OGSI compliant

  6. Online Knowledge Center built from Portlets A set of UIComponents • Web Services provide a component model for the middleware (see large “common component architecture” effort in Dept. of Energy) • Should match each WSDL component with a corresponding user interface component • Thus one “must use” a component model for the portal with again an XML specification (portalML) of portal component

  7. HTML Jetspeed Architecture Turbine Servlet JSP template ECS Root to HTML Screen Manager PSML ECS PortletController PortletController ECS ECS ECS PortletControl ECS ECS ECS ECS ECS Portlet Portlet Portlet Portlet Portlet Portlets HTML Local files JSP or VM Local templates WebPage Remote HTML Portlets User implemented using Portal API XML RSS, OCS, or other Local or remote Data

  8. Portlets and Portal Stacks • User interfaces to Portal 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 (Jetspeed) User facing Web Service Ports Message Security, Information Services Application Grid Web Services Core Grid Services

  9. 4 available portletslinking to Web ServicesI choose two Jetspeed Computing Portal: Choose Portlets

  10. Choose Portlet Layout Choose 1-column Layout Original 2-column Layout

  11. Architecture of Collaborative Interactive Application as a WebService (SVG) SVG content server (Web Service) SVG Document Rendering Engine Collaboration Using software multicastuser ports {JMS, NB} Client Controlling Event Session manager New/Updated Content ChosenRendering& Update SVG portlet Portlet A Portlet B Event Service {NaradaBrokering…} Jetspeed Portlet Control Portlet Controller Turbine Screen Controlling Event New/Updated Content Setup HTML/WML content HTTP request HTTP request HTML content Communication Adaptor for PDAs Controlling Event New/Updated Content HHMS HTTP Client HTTP Client HHMS {JMS, NB} Client HHMS Client Minimum collaborative environment Minimum collaborative environment PDA user Desktop user

  12. File management Tabs indicate available portlet interfaces. Lists user files on selected host, noahsark. File operations include Upload, download, Copy, rename, crossload

  13. Sample page with several portlets: proxy credential manager, submission, monitoring

  14. Administer Grid Portal Provide information about application and host parameters Select application to edit

More Related