Transcript 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.

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
• 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
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 ……..
User
Services
Portal
Services
Grid
Computing
Environments
Aggregation
Portal
Application
Application
Metadata
Service
Application
Service
Portal
Services
OGSA (OGSI) Interfaces
System
Services
Actual Application
System
Services
System
Services
Raw (HPC)
Resources
“Core”
Grid
Database
Web Services as a Portlet
• Each Web 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 portlet
at same time
Application as a WS
General Application Ports
Interface with other Web
Services
WSDL
W
Application or
Content source
Web Service
P
S
R
User Face of
Web Service
WSRP Ports define
WS as a Portlet
Web Services have other
ports (Grid Service) to be
OGSI compliant
Online Knowledge Center built from Portlets
A set of UI
Components
• 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
HTML
Jetspeed
Architecture
Turbine Servlet
JSP template
ECS Root to HTML
Screen Manager
PSML
ECS
PortletController
PortletController
ECS
ECS
ECS
PortletControl
ECS
Portlets
Data
Portlet
XML
RSS, OCS, or other
Local or remote
ECS
Portlet
ECS
Portlet
ECS
Portlet
ECS
Portlet
HTML
JSP or VM
WebPage
Portlets
Local files
Local templates
Remote HTML
User implemented
using Portal API
Portlets and Portal Stacks
Aggregation Portals
(Jetspeed)
User facing Web
Service Ports
Application Grid Web
Services
Core Grid Services
Message Security, Information Services
• User interfaces to Portal
services (Code
Submission, Job
Monitoring, File
Management for Host X)
are all managed as
portlets.
• Users, administrators can
customize their portal
interfaces to just precisely
the services they want.
Jetspeed Computing Portal: Choose Portlets
4 available portlets
linking to Web Services
I choose two
Choose Portlet Layout
Choose 1-column Layout
Original 2-column Layout
Architecture of Collaborative Interactive
Application as a WebService (SVG)
SVG content server (Web Service)
SVG
Document
Rendering Engine
{JMS, NB} Client
Session manager
HTTP Client
{JMS, NB}
Client
Minimum
collaborative
environment
Desktop user
Event Service
HTML/WML
content
HTML content
Setup
HTTP request
Jetspeed
Chosen
Rendering
{NaradaBrokering…}
& Update
Portlet A
Portlet B
Portlet Control
Portlet Controller
Turbine Screen
HTTP request
SVG portlet
Collaboration
Using software
multicast
user ports
Controlling Event
New/Updated Content
Communication
Adaptor for PDAs
HTTP Client
HHMS
Client
Minimum
collaborative
environment
PDA user
File management
Tabs indicate available
portlet interfaces.
Lists user files on
selected host, noahsark.
File operations include
Upload, download,
Copy, rename, crossload
Sample page with
several portlets:
proxy credential manager,
submission, monitoring
Administer Grid Portal
Provide information
about application
and
host parameters
Select application
to edit