1 / 12

Portal Update Plan

Portal Update Plan. Ashok Adiga adiga@tacc.utexas.edu (512) 471-8196. Outline. Update group on on-going discussions with implementation team on Grid Build Status tracking Static vs Dynamic Information in the portal Resource Information in the portal Documentation organization.

eric-hensley
Download Presentation

Portal Update Plan

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. Portal Update Plan Ashok Adiga adiga@tacc.utexas.edu (512) 471-8196

  2. Outline • Update group on on-going discussions with implementation team on • Grid Build Status tracking • Static vs Dynamic Information in the portal • Resource Information in the portal • Documentation organization

  3. Build Status • Grid Build status reports • Spreadsheets e-mailed at beginning of month • Tracking status on resources and applications • Follow-ups via email and phone • Kate Barzee is helping us with tracking status • Please send your status if you haven’t yet done so • Update spreadsheet OR simply email your status

  4. Static vs Dynamic Information • Dynamic Information in portal today • Status, Load, Jobs on Resource page • Everything else is static • Will make Portal change to make this clear • Status arrow summarizes availability of • Globus/GRAM, gridftp, MDS grid services • Test scripts run remotely as “sgmonitor” user. • Will make arrow clickable for detailed information • Add test for environment variable test? • Long term possibilities • Query software stack on each resource

  5. Portal Resource Information • Current Resource page will be modified to add information about • Software Stack • OS & version • Globus version • Local Scheduler (PBS, LSF, etc.) • Contact Information • Name, email, Phone, response-by information • Remote access to resource information • Portal uses GPIR repository • See documentation at http://gridport.net/services/gpir/ for details on web service access to resource information

  6. Online Documentation • Information available in various forms/locations • SURAgrid web site • SURAgrid portal • Several documents • Consolidate all information for easier access • Meet user needs • Easier to maintain/update • Must support multiple types of content owners • Portal admins, Web admins, Site resource admins, and application owners • Currently being designed by SURA

  7. Use Cases • Application Users • What is SURAgrid? • How do I setup to use SURAgrid? • What resources are available? • What applications are available? • How do I move files between resources and submit a job? • What is the status of my job? • Resource & application administrators • How do I add a resource to suragrid? • What is the status of suragrid resources? • How do I enable a new application to run on my resource? • Grid Administrators • Resource Status • Project status

  8. Portal Information • Writable by portal admin only: • portal setup documentation • creating a portal account • registering proxy certificate w/myproxy server • adding a resource to the portal • minimum resource requirements • steps to add new resource to suragrid • resource information (status, description, etc) • contacts for support issues, authorization setup, etc.

  9. SURA Web Information • Writable by SURA web admin only: • overall suragrid docs – mission, vision, usage policy • Status reports (about resources, applications, etc.) • documentation on common functions such as: • environment variables • how to setup and run new applications • applications documentation (could be hosted by Application Owner) • list of supported apps • list of resources running each application; • links to detailed application descriptions • application support contacts • User Forum? • Wiki?

  10. Site Resource Information • Writable by resource admin at each site • maintain resource specific information • hardware configuration • software stack • procedures for getting an account • example usage for submitting batch parallel job • contact information for support w/service level expectation • applications available (?)

  11. Application Information • Writable by application owner • Status • pre-requisites • installation • usage

  12. More About TACC: Texas Advanced Computing Center www.tacc.utexas.edu info@tacc.utexas.edu (512) 475-9411

More Related