Hi Raman, On Tue, Apr 3, 2012 at 5:02 PM, Raminderjeet Singh <[email protected] > wrote:
> See my comments inline. > > Thanks > Raminder > On Apr 3, 2012, at 4:39 PM, Lahiru Gunathilake wrote: > > > Hi Devs, > > > > I am thinking of improving the usability of the document registration > > (host,service,deployement) to make the life easier for the Science > gateway > > users. > +1. Yes we need to improve user experience as users normally get lost with > multistep process. A simple form should definitely help with less buttons > and pop up menus to fill some information. > > > > Users will fill out only one form not 3, User simply have to register a > > service ... > > > > User will tell what is the input parameters looks like (parameter > Name/type > > - comes from a drop down) > For user point of view its application with input and output parameters. > We create a web-service for application, which is internal to Airavata > architecture. > > > > We will make it optional to register the host description, so we will > > defined the host descriptions for the given set of Super computers, users > > just have to select from a dropdown, if user adds a new one it will pick > it > > from the registry and will be displayed in the dropdown. > With a option for the user to view/update the information if needed and > add there local clusters. Some of the endpoints are updated over time or > additional endpoints are added. > > > > Then user will tell where is the actual script located in the grid > > (Executable location). > > > > User doesn't have to give any scratch location (If user want it can be > > configured but by default user doesn't have to ) We will derive a scratch > > location (temporary location to store the inputs/outputs) from the given > > script location. (In the UI we need to show the derived temp location.. > if > > user doesn't want that location to be the temp location users simply have > > to edit it) > +1 very much needed as it again GFAC requirement not user application > requirement. > > > > User have to give the RSL parameter, more specifically the project Name > ... > > other parameter will be filled based no the selected host.. But mostly we > > expect users to fill out the Queue Name, Job type etc. > All these important parameter need to be exposed at workflow level also as > based on input/problem size user can define where he want to run its > application using how many processes and queue name. There are some > additional RSL parameters like Job name, email id, email params etc can be > also very useful to user. > Can you please point me to all the RSL parameters users can configure ? I don't think current XBaya UI has everything. Lahiru > > > > > If you have any concern about this please provide some input... > Currently if user submits a job and want to kill the running job user need > to login to resource to kill the job. Xbaya should have a service to kill > the running job. > > > > > Thanks > > Lahiru > > > > > > > > -- > > System Analyst Programmer > > PTI Lab > > Indiana University > > -- System Analyst Programmer PTI Lab Indiana University
