IOE Technical Meeting, 26 August 1999 at NPAC, Syracuse University Participants ARL: Derek Moses NCSA: John Melchi, Doug Fein NPAC: Roman Markowski, Yuping Zhu, Jungkee Jake Kim Agenda 8am - 2:30 pm * Overview of results from Management Teleconference (25 Aug 99) * Overview of available technologies related to the project * Tom Haupt's presentation (Gateway, WebFlow) and preliminary discussion of integration into portal - 40 min * Discussion (Portal components) * Security * Interfacing * Calendaring * Document repository * Server Setup and Hosting * Email Repository / Discussion Forum * Project Tracking System * Training and Management Training * Other DOD projects * Synchronous Collaboration * Other issues * Communication channels Overview of available technologies ---------------------------------------------------- Each Technology currently available was discussed for possible uses within the projects and interactions with the project. * Oracle 8i (JDBC, SQL, SQLJ) * XML, XSL, XSLT, DTD * Java, JavaScript, servlets * WebServers: Apache(SSL), Oracle Application Server * SSL, Kerberos, PKI * Portal, Multitier Architecture * J2EE: http://java.sun.com/j2ee * Webflow: http://www.npac.syr.edu/users/haupt/WebFlow * (Presentations -> HPDC-8) Security ------------ The IOE web system needs to be secure to the ARL, ASC and DOD standards we are therefore planning for the strongest level of security the web can provide. We are also looking into the future security plans for the web and internet. Goals : * Authentication: Kerberos based * Public Server and secure IOE server * Kerberos Apache API Deliverables * Oracle 8i has built-in security (Oracle Advanced Option: Kerberos, SecureID, Radius, SSL); testing * Web integration and PKI - testing * Description of Security groups for access restrictions * White Paper on Final Security Structure Timeframe: 5 months Interfacing --------------- One of the most important things in any workspace is the human-computer interfacing. Based on mainstream technologies of the portal, we are creating a customizable interaction that will feed more information to users more easily than other technologies. We are basing this system on XML modules for user interaction. Goals - Graphical User Interface (graphic artist is working on it) - many XML modules feeding one HTML page for display - Customization based on - personal needs and security customization Timeframe - first prototype exists: http://aim.ncsa.uiuc.edu - prototype for SC'99 (GUI, XML modules) and for Directors - meeting (mid Dec 99) - Modifications on request Future Plans (possibly CY5) - Scientific Notebook - tracks state info - logs of all actions (possible replay of sessions or daily routine) - personal XML module that gives external connections (weather, hpcwire, news, etc.) Calendaring --------------- With management of the PET program and the MSRC you have a large amount of date specific information. One of the goals of the IOE is to integrate this date specific information in one calendar interface. This would be a system that read project goals, budget deadlines, training events, and personal calendars through XML interaction. A system like this will allow all pieces of the project to interact with the dates and calendar setup. Goals - Oracle + XML parsing-based system - Looked at Commercial Calendars for technical capabilities - Meeting Maker, Lotus Notes, Office Schedule+, Exchange Saver Requirements - we need web-based calendar which includes notification - we also need to have a calendar that can interface with any database to pull out relevant info, and interface to XML - NCSA and NPAC are using Lotus Notes but want to replace it with something else Timeframe - For SC'99 - Front-End interfacing - data stored in single DB - 4 Views (day, week, month, year) - 3 Initial categories (Training, General, People's Schedules) - we need 6 months for XML specification - End of Year 4 - Data stored within any IOE DB - XML parsing for information - personalized display - additional categories implemented - personal category creation and interaction Document repository ------------------- The Document repository is a system for cataloging and storing all documents that relate to the pieces that interact with this project. The idea being a system that will store and catalog documents for search and interaction with the other database applications. Goal - GUI for submission of existing files or created on the fly - searching, listing - versioning Requirements - we need user information about document types - (PS, TEX, PDF, DOC, XML, HTML, JPEG, MPEG, MOV, etc.) - what will be stored and how much disk space - manuals, clips, etc. - access restriction (for submission, viewing) - some with general access: software manuals - other restricted to people, groups Timeframe - Oracle iFS will be released by end of this year - Initial demo for SC'99 - based on Oracle 8i and InterMedia - initial doc entry from Web - 5 months Specification for Data related to documents (doc types, who can list, how sort, metadata; sort criteria: organization (ARL, ASC, PET), program, type (success story, report, budget), project, submitters, authors, doc type (word, ppt, etc.), size, access rights) - 7 months - UI from Intermedia to be redone by designer - testing various additional data types (some already verified) - Document entry from the web - Highlighted Keyword Search - GUI for Browsing Files - Locking mechanism Server Setup and Hosting ---------------------------- Hardware - NCSA excellent network connection - can provide support 24/7, but no need in intial testbed state - experimental/development machines at each site - NPAC: Sun Ultra 450, 4 processors, 30 GB HDD, FDDI Oracle 8i, Apache, OAS - NCSA: Intel Dual PIII, Linux or NT Firewall - NPAC - no - ARL - no - ASC - yes - NCSA - yes (partial, screening traffic) Software - Oracle 8i - recommended as the best SQL database - Apache(SSL) + servlets (Stronghold or mod_ssl) - Oracle Application Server (no servlets) Timeframe - testing : NCSA, NPAC, ARL - January 2000: Production-testbed in NCSA - real production system require some additional funds for 24/7 hosting and consulting Email Repository/ Discussion Forum ------------------------------------ We need clarification from ARL and ASC what functionality and scope they expect/want Options include: - Minimal email lists archived as identified - Most/All email lists archived - Threaded discussion forums (HyperNews) - Majordomo-based Security and access control very important Timeframe - we can integrate with existing mail system within 6 months - In 12+ months we can include personal email Project Tracking System ----------------------- This is perhaps the most important MIS application of the IOE. This project will the drive the integration of all the smaller applications within the project. We created a timeline for this with space to help create a project definition that can be used my all the MSRCs. The project tracking system will also use data from the document systems, and will feed information to the calendar and training databases. Problem: - we need more information about current Project management workflow in ARL and ASC - ARL and ASC should have the common approach for project processing (Key fields should match, some variance in details) - EJ should provide this information for ARL and initial system - What kind of reports? (techical, trip, various status) - What type of documents? (proposal, SoW) - Some documents are created (Word) and submitted to the database, - others created on the fly (web forms) - Proposal: Contact Info, Objective, Description, Deliverables, - Customer, Benefit to the WarFighter, Risk, Funding Timeframe - Short Term: graphical interface revised - November 1999: specification of requirements - January 2000 : database (Yuping); we can start feeding - database and revise current technical architecture - April 2000: Graphical interface and interactive Training and Management of Training ----------------------------------- This will involve interaction with the Training database being designed and developed at NPAC for ASC. This will also interact with systems that Derek Moses has in place at ARL. The important issue is integration of training information with the other major projects of the IOE. Goal - training calendar - connection with Doc Repository (notes, assignments) - evaluation of courses - registration - customizable stats reports about courses - connection to personal calendars - course information Timeframe - Step 1. study of integration with ASC Training - system developed in NPAC and existing ARL Training System - Step 2. implementation in 6 months - registration, evaluation, course information - Step 3. implementation in 12 months - training calendar, connection to Doc Repository - connection to personal calendar Other DOD Projects for possible integration -------------------------------------------- Remedy (User Support) RIB - Will look at new release v2.0 Gateway - Initial talks underway Synchronous collaboration -------------------------- We focus on Tango as the most robust Other issues -------------- Communication between members of technical team Tango:Brian Roach (broach@ncsa) will install The second majordomo list for technical developers pet-ioe-tech@npac.syr.edu HPC User Support functionality and repsonsibilities needs to be defined in cooperation with Gateway project