Given by Geoffrey C. Fox, Wojtek Furmanski at Analysis of ASCI DRM Design on August 98. Foils prepared September 13 98
Outside Index
Summary of Material
We comment on Sandia DRM preliminary document and attach three background presentations describing |
1) Community project to define standards for seamless interfaces allowing universal access to general hosts
|
2) NPAC's hierarchical access Gateway multi-tier architecture and illustrate it with |
3) NPAC Projects using NPAC's WebFlow and JWORB object broker combined with Globus to illustrate viability of hierarchical model for NCSA (NSF Alliance) and DoD HPC modernization applications |
Outside Index Summary of Material
September 5 98 |
Geoffrey Fox |
Northeast Parallel Architectures Center |
Syracuse University |
111 College Place |
Syracuse NY |
gcf@npac.syr.edu |
http://www.javagrande.org |
http://www.npac.syr.edu/europowsept98 |
http://www.npac.syr.edu/users/gcf/jgeurosept98 |
We comment on Sandia DRM preliminary document and attach three background presentations describing |
1) Community project to define standards for seamless interfaces allowing universal access to general hosts
|
2) NPAC's hierarchical access Gateway multi-tier architecture and illustrate it with |
3) NPAC Projects using NPAC's WebFlow and JWORB object broker combined with Globus to illustrate viability of hierarchical model for NCSA (NSF Alliance) and DoD HPC modernization applications |
We have two major comments on overall architecture |
Firstly it does not appear to include some commodity services such as collaboration, training, consultant interactions, (commodity) database, "personal web server" |
Secondly it suggests a uniform architecture whereas we suggest designing for a hierarchical system supporting different protocols, performances and capabilities at each level or tier (terminology used later)
|
1) In first foil (criteria/principles) we suggest adding
|
2) We suggest that the establishment of an agreed object model for jobs and computers (or more generally resources) is implied by architecture
|
In resource material at end, we define 3 basic tiers
|
Sandia CPLANT machines would appear in both gateway and backend tiers
|
As described in following, we suggest gateway can be viewed as linked servers -- each hosting some sort of service -- and linked either by user-set, agent negotiated or fixed channels |
Sun's new JINI resource management system seems possibly very important |
Globus/Legion and others have identified difficulties stemming from existing batch schedulers such as LSF and Codine which do not immediately support synchronicity between jobs on different machines as is required in metacomputing
|
Do you need services such as WebFlow in following foils which supports composition of compound jobs or metaproblems? |
The Gateway would be distributed with systems deployed at each site
|
1) Description of "Java Seamless Computing Framework" |
2) Description of "GrandeGateway" hosting "Grandecomputers" as developed for four DoD HPC modernization sites and slightly modified for Sandia |
3)WebFlow over Globus NPAC project illustrating hierarchical concept |
Allows Universal Access to all computers from the same Java Applet Front End |
Infrastructure for Metacomputing, Performance Modeling, Interfacing computers and data to distributed computational objects |
We expect to hold soon an open meeting sponsored by Globus and Java Grande Forum (working group led by Dennis Gannon) to start definition of these ideas |
To be realized as Java Interfaces; CORBA IDL or XML |
Java Calls (mainly Interfaces and not methods) to capabilities expressed in implementation neutral form |
Drivers convert these general calls to vendor specific implementation of service |
Java code can either be all on client (2-tier) or on client and middle tier (3 tier) |
e.g. JDBC (Java Database Connectivity) is a universal interface to all relational databases |
Adoption of this JDBC implies that vendor specific solutions are immediately less attractive
|
Java applications |
JDBC API |
JDBC Driver manager |
JDBC API |
JDBC Driver API |
Enables development of Web Interfaces to run a given job on any computer with any data source compliant with this framework just as JDBC gives a universal interface to any relational database
|
The Computing Services Framework will allow vendors to compete on either User Front End (GUI) or back end services with the JavaCS framework providing universal linkage |
The framework is implemented at the backend as a set of drivers which map generic Java Interfaces to particular software (e.g. a compiler) on particular machines. |
Requires agreement by "suitable interested parties" on
|
"Old" (seamless workshop Sept 97) link is http://www.sis.port.ac.uk/~mab/Computing-FrameWork/ |
Abstract ideas developed in Condor Globus Legion and PACE POEMS PetaSIM for harder problems (metacomputing / performance specification) and developed for seamless problem by Sweb (Cornell) WebSubmit (NIST) or UNICORE (Europe) |
Compiling, Executing, Specification of features needed for execution optimization
|
Accounting -- integrate with Web commerce technology? |
Authenication, Security (especially hard in metacomputing as link several different management policies)
|
Sharing, Accessing and Storing into File Systems |
Data and Performance Visualization Interface (how applets access server side information) |
Performance measurement and recording (cf: Pablo SDDF) |
Interfaces for Programming Tools
|
Libraries including names in generalized Math class and
|
Resource Discovery, Allocation and Scheduling
|
Module linkage model for metaproblems (multidisciplinary applications) -- can we use standard JavaBean approach? |
Middle Tier (Business) Logic links user and system view of data and services |
Generalized distributed object (database record is "just" a distributed object) specification |
Different but linkable transport protocols |
Client |
Client Tier Middle (Gateway) Tier Back End |
High Performance Computing and Communication Tier |
Clients |
Gateway Systems as Middle Tier |
Database |
Matrix Solver |
Optimization Service |
MPP |
MPP |
Parallel DB Proxy |
NEOS Control Optimization |
Origin 2000 Proxy |
NetSolve Linear Alg. Server |
IBM SP2 Proxy |
Gateway Control |
Agent-based Choice of Compute Engine |
Multidisciplinary Control (WebFlow) |
Data Analysis Server |
We have multiple supercomputers in the backend -- one doing CFD simulation of airflow; another structural analysis while in more detail you have linear algebra servers (Netsolve); Optimization servers (NEOS); image processing filters(Khoros);databases (NCSA Biology workbench); visualization systems(AVS, CAVEs)
|
All linked to collaborative information systems in a sea of middle tier servers(as on previous page) to support design, crisis management, multi-disciplinary research |
Seamless Interface -- an Enterprise Javabean which processes input from user's Java Applet interface and maps user generic commands to those on specific machine
|
Coarse Grain Resource management of heterogeneous MPP backend (linked to seamless interface) |
Performance Estimation Service |
Database and Object Brokers; Network servers like NetSolve |
Collaboration Servers such as Habanero, Tango, Lotus Notes ... |
Visualization Servers |
"Business Logic" to map user data view (e.g. objects) to persistent store (e.g. Oracle database) and simulation engine (MPP) preferred format |
The 90% of users who only need HPCC occasionally |
Any commodity applications such as modern enterprise information systems |
The collection of (Java) servers using commodity protocols -- including IIOP HTTP etc. -- and providing key services not necessarily requiring high performance (MPP's available in backend tier if high performance, large storage etc. needed) |
Most of a Command and Control Application which would then interface to backend computational service (e.g. to simulate crisis as in Los Alamos Delphi project) |
Several FMS (Forces Modeling) and IMT (Integrated Modeling and Testing) DoD Applications i.e. DMSO style distributed simulation |
Some I/O Intensive applications |
High value services with modest computational needs e.g. grid generation and other pre-processing, data manipulation and other post-processing |
Video Servers and multi media databases for Training |
Design and Planning Tools -- programs that could be on client but in multi-tier "thin-client" models are run as middle tier services |
Processors (Java servlets) for JSCF (Java Seamless Computing Framework) and proposed (by NPAC) HLA/RTI control services |
"Glue" for Multidisciplinary Interactions |
Control of Metacomputing applications |
JINI Java Resource Registration and Discovery Service |
The following diagram illustrates features of the "gateway concept" |
The hardware to support gateway may be different from that natural for HPCC backends
|
Several services would be controlled in "GrandeGateway" -- we illustrate this for collaboration which would allow sharing of information from clients and also backend Super(Grande) computers represented by proxies (e.g. Java or CORBA wrappers) at this level
|
There is no clean 1:1 mapping of hardware and software tiers
|
Geographically |
Distributed |
Grandecomputer |
Resources |
GrandeGateway |
System |
hosting Seamless Access |
TangoInteractive, |
Visualization and other Services |
Geographically Distributed users |
and consultants |
High Speed HPCC Network Nexus etc. |
Commodity Network IIOP HTTP etc. |
NPAC Project illustrating multi tier Gateway incorporating Java Applet Program Composition at Client |
DMSO HLA/RTI Compliance (FMS,IMT) |
CORBA COM Java Web Interoperable Gateway GLOBUS High Performance Backend inherits Gateway Services: Collaboration, Distributed Objects, Databases, Visualization ..... |
Client (Tier 1): Java Graph Editor for Webflow linked to interpreted debuggers, visualization, performance estimation and other client side tools
|
Middle Tier 2: Network of JWORB or Java Servers running on Gateway Tier linking to CORBA COM and HTTP(Internet)
|
Back-end Tier 3: Simple MPI or Globus (or similar) where available and where necessary |
Next foils show
|
Client Tier |
IIOP High Functionality |
Middle Tier |
Future Globus |
Globus |
Future Parallel I/O |
WebFlow |
server |
WebFlow |
server |
WebFlow |
server |
EDYS |
CASC2D |
Data Retrieval |
High Performance SubSystem |
CASC2D |
proxy |
IIOP |
Web Browser |
Data Wizard |
WMS interface |
Toolbar |
HTTP |
WMS |
File Transfer |
File Transfer |
GLOBUS |
Internet |
WebFlow modules |
(back-end) |
WebFlow |
middle-tier |
WebFlow applet |
(front-end) |
JWORB - Java Web Object Request Broker - multi-protocol middleware network server (HTTP + IIOP + DCE RPC + RMI transport) |
Current prototype integrates HTTP and IIOP i.e. acts as Web Server and CORBA Broker
|
Next step: add DCE RPC support to include Microsoft COM |
JWORB - our trial implementation of Pragmatic Object Web |
First non DMSO implementation of RTI -- HLA (distributed event driven simulation) Runtime |