Given by Geoffrey C. Fox at Gateway Workshop Aberdeen Maryland on 24-25 May 99. Foils prepared May 26 99
Outside Index
Summary of Material
Discussion at Gateway Meeting Aberdeen including notes and brainstorming on future of Gateway |
Outside Index Summary of Material
NPAC |
111 College Place |
Syracuse NY 13244 4100 |
Phone: 3154432163 |
May 24 25 1999 |
Aberdeen Md. |
Geoffrey Fox |
Syracuse University |
Discussion at Gateway Meeting Aberdeen including notes and brainstorming on future of Gateway |
There are existing databases at MSRC's with lists of installed software such as Gaussian |
These need to be fed in (with Jini like mechanism) to Gateway system -- note each MSRC will and can use different internal formats but export to Gateway in common format |
Gateway has a user/group profile, history mechanism cf. Tango needs |
Currently by hand event model to be replaced by CORBA event model |
there is a tag called connection in task specification invoking events |
Ken's "database" is really an XML file or equivalent |
What is front end model for an application |
Edit data file; enter data into HTML form; take defaults from user database/profile |
Net result is abstract task specification |
What happens if there is a failure
|
Exception Event Handling should be part of Gateway |
Role of Scientific Notebook |
XML makes searching easier |
Ken has a training XML structure |
xmlspy program analyzes XML documents; creates DTD's |
input parameters need
|
history needs to record where user was in documentation via bookmark -- her state |
Accounting needs to be globalized
|
Chemical Engineering workbench want to edit code rather than input data through files
|
In visualization HDF defines data model at level roughly of Fortran or C variables includes name=value |
DICE and DoE (more generally) are defining higher level constructs like sets and grids |
There are no agreement on visualization output like isosurfaces |
Multiple layers controlled on Server side with XML and HTML
|
Uses Perl CGI to convert XML to HTML using capabilities of browser down to 3.0 |
Will probably use flat files to store user state so it is restored to previous state |
Lotus Notes supports COM and DCOM objects -- Apache won't do this |
Security and User Interface are key features |
RIB 2.0 switching to MiniSQL |
Linking RIB Software and Hardware data models with Globus so can invoke software from RIB |
Interoperation between RIB's done by exporting XML files |
ARL and ASC have (separate from RIB) software configuration databases |
ASCI Scientific Data Management SDM Project (30 people within DoE!) will be linked with RIB |
NetSolve linked to Scirun for computational steering |
NetSolve is Client Server not hierarchical |
Will have Globus and non Globus version |
Netbuild |
ARL NetSolve proposal is standalone |
ASC Proposal is to break NetSolve into client, agent (middle tier), backend (NetSolve Server) |
DoD Metacomputing: 4 Tier so that can separate Configuration Management and Server Control |
Phase 1: Define and Establish Testbeds |
Phase 2: Initial Implementation |
Phase 3: Initial Deployment |
Metacomputing Workshop Late Summer 99 sets up working group and identifies issues |
Phase 1: Set up CCM and IMT as test applications |
Install and use Legion and Globus |
NSF NASA DoE Linkage |
Phase 2: SRC = MSRC +DC issues, further applications |
Phase 3: Deploy meta-queuing, training |
Subsurface IPARS with multiple models
|
CEWES Shallow Water 3 codes |
PARSIM hooked to PV3 now |
All commercial codes of this type linked to Oracle
|
Database and Simulation |
Visualization -- Tekplot and AVS (Immersadesk plus wand) |
AVS 2 weeks |
Argonne using lower level visualization tools? |
PARSIM with Gateway AVS Database -- NPAC OSC |
IPARS NetSolve and Netbuild -- UTK |
Review where we are September |
Program running v development |
Programs with files input and output
|
Databases |
Programming models
|
Defining Interfaces |
CCM |
Visualization
|
Multiple backends
|
T and E (IMT) Application
|
services
|
Link to Information services |
SC99 critical for buy in |
Easy to add applications
|
Multidisciplinary support |
Need simple program distributer talking to Globus |
In general link to ASCI Alliance NASA .... Efforts |
Quantify and elaborate Gateway Architecture Interfaces Standards
|
Base Plan: CCM plus core Gateway plus visualization accessing multiple backends for SC99 |
Option I: Study and Documentation of Architecture, Interfaces and Use -- define Gateway compliance of all three layers |
Option II: Some demonstration of ease of adding additional codes or backend resources to system either within PSE or with default PSE |
Option III: Add a "distributer" to give intelligence to choice of backend |