Version 3 (modified by 15 years ago) (diff) | ,
---|
- Toni
- Extensions - requirements are training
- perspective - web interface is not general enough
- GPU Grid's Soap interface is general enough
- David
- User Defined in this discussion is the Scientist
- Different categories of users
- Envisage a context where random volunteers can submit
- Need to control the scripts where users can inject viruses
- Toni
- Users should not have ability to upload applications - this is a security risk
- Applications that accept scripts should be tightly restricted
- Christian
- Extend template files w/ additional text.
- Soap can be used for a web page where scientist selects for application to submit
- Scientist must provide a template
- Toni
- Webpage for submitting:
- Does not lend itself to batches
- Output would not be able to retrieve on webpage
- Webpage for submitting:
- Christian
- Suggested a structure where input is packed in an archive, uploaded to the server, uncompressed and used by job creation script
- Zoltan
- Change Execution soap website
- Client executes application
- Master feeds the work
- Toni
- Described how GPUGrid accounts for the priority of workunits. High priority starves the lower priority
- Will release the Perl code
- Does not deal w/ scheduler code
- One should have a scientist's table that tracks various project scientist information relevant to submissions
- David
- Many options [for scientist's table], eg accounting, controlling latency, throughput
- Toni
- Not many scientists on GPU grid currently
- Micheal Weber
- Leiden Classical has a drop-down menu
- submissions interface w/ limited characters
- Registers the heavy users
- David
- Is Leiden a generic solution?
- Christian
- Leiden uses a separate configuration file
- Toni
- Computes the has of the file, avoid copying files, conserve space, use hard links in the download directory
- Kevin
- There should be a common mechanism to submit
- Zoltan
- How to submit work remotely
- David
- It would be good to have a standardized way
- Toni
- Use MD5 checksum on the input files, store the hashes on the server
- Jack
- What if there were a script to generate the templates, where user is prompted for various parameters?
- David
- Not the bottleneck for scientists
- Need to move the WU Generator and Assimilator off the server
- Keep the things we trust stay on the server