1 / 12

The NAZO Solution

The NAZO Solution. Alex Nicoll. Senior Technology Research Fellow. College of Information Science and Technology. University of Nebraska at Omaha. Development Guidelines. No complex languages No scripting User Friendly Flexible Secure Multi-platform Above all – FAST. Components.

sibley
Download Presentation

The NAZO Solution

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The NAZO Solution Alex Nicoll Senior Technology Research Fellow College of Information Science and Technology University of Nebraska at Omaha

  2. Development Guidelines • No complex languages • No scripting • User Friendly • Flexible • Secure • Multi-platform • Above all – FAST

  3. Components • Security • Web Interface • Database • Scheduler • Job Execution Engine • Inter-Cluster resource sharing

  4. Architechture • Master Node – • Scheduling Engine • Web Server • Small user base • SSL key based communication • Packet Filtering Bridge • Nodes • Job Execution Engine

  5. Packet Filtering Bridge? • IPSec Enabled • Transparent • Fast Response • Removes Crypto Burden To Internet Packet Filtering Bridge Client Node Client Node Master Node Client Node Client Node

  6. Log In Flow of Job Submission Refresh Select Application Submit Job View Submission Status Log Out

  7. Flow of Job Execution SQL Application Table Updated Job Submitted Master SQL Table Updated Job Placed In Queue Job Executed Input/ Output Files Deleted Inputs Validated Master SQL Table Updated SQL Application Table Updated Input Files Created

  8. Job Deletion Retrieve Job Status From Master Table Delete Record From Application Table Delete Record From Master Table Done Pending Delete Job From Queue

  9. Master Job Table • Job ID (created when job is submitted) • Job Type (application) • User ID • Queue ID (created when job is queued) • Job Name (user specified) • Time Queued • Time Started • Time Ended • Job Status

  10. Application Table • Queue ID • Job ID • Inputs (files as globs) • Outputs (files as globs)

  11. Other Features • User Initiated Database Updates • Application Parameter Storage/Re-Use

  12. Future Plans • Applications as web templates • More applications • Partner cluster “reservations” for nodes • Suggestions?

More Related