SWIM WEB PORTAL by Dipti Aswath SWIM Meeting ORNL Oct 15-17, 2007

SWIM PORTAL DEPLOYED “FOR JAGUAR” WILL ADDRESS SEVERAL PROJECT ISSUES Don listed numerous high priority issues for the SWIM Project Need more users and more physics runs − Portal designed to lower barriers for launching SWIM physics runs − New users can include the experimental community We need to get everything ported to Jaguar − Jaguar “security issues” need to be resolved and a decision reached on the entire portal feasibility We SWIM specific publications − Does a publication that discusses the SWIM portal integrated with framework and running a physics code help here? We need monitoring and data retrieval tools − Monitoring and meta-data examination done within the portal We don’t yet have a system for handling the data we generate − Meta-data is handled by Obsidian, queries from the portal − Meta-data has data file location, no transfer mechanism at this point

Vision: Simulation Components Available to a Wider US Fusion Community via Web Clients The SWIM Web Portal is working towards realizing the vision − Prototype is operational Goals that will enable the vision to be fulfilled − SWIM Portal with web clients intended for convenience to physicists and not as a single required entry point − Browser Interface for easy data access and remote component submissions − Secure authenticated and authorized access for scientists to make and monitor component runs − Distributed authorization allow stakeholders easy control over resources

SWIM Federated Web Portal User Authentication XEventChannel Metadata (events) Data Manager Web Events Web Service mySQL Internal schema External schema Elvis Displays User delCred (single sign-ons) Framework AORSA TSC CQL3D M3D NIMROD Framework PPPL (/p/swim/portal) Remote Job Launch via Portal (portal_launch.py) swim_launch.py batch_mgt_ script.py fsp.sh Architecture : Web Portal Prototype Portal interaction with modules ROAM (AuthZ) Interaction between modules ROAM : Resource Oriented Authorization Manager

Prototype Operational Web Portal Services Services Provided: Secure authenticated and authorized accesses transparent to the user Platform to instantiate simulation runs remotely and monitor its run A meta-data manager to archive and retrieve meta-data information (as per user query) resulting from the runs. Meta-data is data about data (e.g. the file name of the data file, its location, and size, are all meta-data)

Prototype Portal Services (1) Security (transparent to the user) − Authentication : User signs on securely with FusionGrid credentials- an id and password, operated by ESnet − Authorization : Component service provider checks to see if authenticated user is authorized to access its service Component Submission and Monitoring − Platform to securely initialize and instantiate simulation runs on remote systems at PPPL (transpgrid.pppl.gov) − User ability to monitor the run launched remotely via events notifying the user on the status of the component run − Browser visualizations / displays of run results

Prototype Portal Services (2) Meta-Data Management − Automated generation and storage of metadata resulting from the runs to enable users to quickly retrieve information on runs made − Monitor run directories and store/extract information such as location, size, timestamp, owner as external meta-data and physics quantities of interest to users as internal meta-data − Relational schema (similar to D3D’s Code Run Database) uses: - Plasmas Table (contains an entry for every run made) - Aorsa_Details Table (handles internal meta-data for AORSA) - Codes Table (an entry for every simulation code) - File Object Table (handles external meta-data and contains information such as location, size, owner, type of the resulting run output files) - FSP_IUEvent Table (categorized sets of Events published for a run)

Prototype Status

We Propose the Following Next Steps Understand the security model required for Jaguar − Are FusionGrid credentials, certified by ESnet, acceptable? − Is MyProxy credential repository server acceptable? − Do all hosting servers (ROAM authorization, Obsidian data manager, Event manager, MyProxy, Pubcookie login, MySQL database, Apache Web Server) have to be located at ORNL? Meta-data enhancement − Enhance relational schema by adding physics quantities of interest − Have real code runs generate meta-data and archive via portal Deploy prototype data management system –Portal is one possible entry point Deploy production portal for SWIM physics runs on Jaguar

Project Decisions and Developer Input Required before Next Steps Commence Acceptable Jaguar security infrastructure must be specified Things needed from SWM physicists − A meta-data file that contains physics items that can be queried from within portal − Design decision on framework/portal integration scheme More feedback as components and services come online