Task #40

GUI refining

Added by José Luis Vázquez Poletti over 2 years ago. Updated over 2 years ago.

Status:Closed Start date:2009-08-21
Priority:Normal Due date:
Assignee:Srinivasan Natarajan % Done:

100%

Category:- Spent time: 50.50 hours
Target version:-

workflow.png (513.8 kB) Srinivasan Natarajan, 2009-07-09 22:38

jtgen.png (535.5 kB) Srinivasan Natarajan, 2009-07-23 23:14

accountdetails.png (624.5 kB) Srinivasan Natarajan, 2009-07-23 23:14

host_queue.png (619.5 kB) Srinivasan Natarajan, 2009-07-23 23:14

workflow.png (645.3 kB) Srinivasan Natarajan, 2009-07-23 23:14

History

Updated by José Luis Vázquez Poletti over 2 years ago

  • Status changed from New to Assigned
  • Assignee set to Srinivasan Natarajan
  • Start date changed from 2009-06-28 to 2009-08-21

As stated in Development Roadmap.

Part of this has already been done. This task will last until 1 week before the end of the project.

Updated by Srinivasan Natarajan over 2 years ago

Dag file is used by gwdagman utility for job submission. Basic GUI and functionality is designed using two gtktreeview for using parent and child relationship and one gtktextview for displaying the contents of the dag file.

Updated by Srinivasan Natarajan over 2 years ago

The changes are made to support tool bar in the existing JT generator. The existing layout must be changed to support frames and toolbar. The options for opening an existing JT file, creating a new JT file, resetting the JT fields, saving the JT file and quitting the application are added.

Updated by Srinivasan Natarajan over 2 years ago

The DAG work flow can be implemented for thin client as follows

  • Generate the dagman file using the gui
  • convert the dagman file to dot file using
gwdagman -d test.dag > test.dot
  • convert the dot file in to png files using grapviz (-Tpng can be used to convert the dot file in to png file)
dot test.dot -Tpng -o test.png

Alternatively the user can choose to view it in ghostview utility. The dot file needs to be converted in to post script file(ps).

This can be done by converting dot file to ps code and piping it to ghostview utility

dot test.dot -Tps | gv -
  • The png files can be then loaded in to the gui using GdkPixbuf

Updated by Srinivasan Natarajan over 2 years ago

The Graphical User Interface is refined to support information more visually using frames,there by adding new options for retrieving data rather than populating it when the page is selected, icons for the buttons or using stock buttons,optons for refreshing the data fields etc... The implementation is done for these new options and for modifications of existing gui.

Updated by Srinivasan Natarajan over 2 years ago

  • % Done changed from 0 to 20

The changes are made to support tool bar in the existing dag workflow. The existing layout must be changed to support frames and toolbar. The options for opening an existing dag file, creating a new dag file, resetting the dag Gtktextview and GtkTreeview, saving the dag file and quitting the application are added.

The changes are also made to ensure visual dagwork flow is generated when the user launches generate work flow.

Updated by Srinivasan Natarajan over 2 years ago

Attached below the snap shot of Dag work flow

Updated by Srinivasan Natarajan over 2 years ago

The additional changes are made to the dag workflow gui to support

  • User selection dot file for the corresponding dag file
  • Generation of the dot file
  • Submitting the job using dag workflow
  • Automatic preview for the dag visual workflow which enables the changes in the graph to be redrawn when user makes changes using generate task/dependency

Updated by Srinivasan Natarajan over 2 years ago

The configuration changes are made to ensure that gtk themes are supported in Gridway Gui

Updated by Srinivasan Natarajan over 2 years ago

Updated by Srinivasan Natarajan over 2 years ago

  • % Done changed from 20 to 30

The Job State Information is refined to have two GTkTreeview's to support

  • Job Information
  • Host Information

The additional changes are made to allow option box for the user to select the required option for Job State Information

Updated by Srinivasan Natarajan over 2 years ago

  • % Done changed from 30 to 40

The Graphical User Interface is designed for Rank Generator using a GTKCombobox to display all resource variables
and a Gtktextview for the user to manipulate on the Resource Selection .

The possible values are

HOSTNAME    
ARCH    
OS_NAME    
OS_VERSION    
CPU_MODEL    
CPU_MHZ    
CPU_FREE    
CPU_SMP    
NODECOUNT    
SIZE_MEM_MB    
FREE_MEM_MB    
SIZE_DISK_MB    
FREE_DISK_MB    
LRMS_NAME    
LRMS_TYPE    
QUEUE_NAME    
QUEUE_NODECOUNT    
QUEUE_FREENODECOUNT    
QUEUE_MAXTIME    
QUEUE_MAXCPUTIME    
QUEUE_MAXCOUNT    
QUEUE_MAXRUNNINGJOBS    
QUEUE_MAXJOBSINQUEUE
QUEUE_DISPATCHTYPE    
QUEUE_PRIORITY
QUEUE_STATUS    

Updated by Srinivasan Natarajan over 2 years ago

  • % Done changed from 40 to 60

The Rank Generator is implemented using a new window popped up when user choose to provide resource selection in a separate gui. The resource selection options are selected using the combobox which get displayed on the gtktextview for the user to edit. When the user selects to edit the existing rank changes are made to ensure that previous value is copied in to the gtktextview.

Updated by Srinivasan Natarajan over 2 years ago

  • % Done changed from 60 to 70
  • Changes are made to fetch Job State Information which helps the user to filter the job based on job or array id and Host Information is also displayed which enables user to select the job based on the host information. Additionally, changes are made to support the user to filter job based on user and dispatcher state. The results(filtered job details) are extracted to the gtktreeview.

Updated by Srinivasan Natarajan over 2 years ago

  • % Done changed from 70 to 80

The gui will use the attributes from the .gwguirc (configuration file). Glib's Key-value file parser is used for parsing the configuration file.

  • The LOGINHOST parameter in the configuration file indicates that the GUI is detached as a thin client. It will run at user's machine and communicate via SSH with DRMAA commands, which reside at the GridWay machine
  • Absence of the LOGINHOST parameter indicates that the GUI is running at the remote machine where GridWay is installed

The executable gridgui will look on the same directory where it's located for.gwguirc file to locate the path to temporary and executable directories.

Below is a .gwguirc sample configuration file

[gridkey]
TMP_DIR=/home/srini/Desktop/gridgui/src/tmp_dir/
EXEC_DIR=/home/srini/Desktop/gridgui/src/exec/
HOME_DIR=/home/srini/Desktop/gridgui/
LOGINHOST=gwgui@gridway.dacya.ucm.es

Updated by Srinivasan Natarajan over 2 years ago

  • % Done changed from 80 to 90
  • The existing graphical user interface and implementation for rank generator is replicated for the requirements Generator. Additionally, one missing field HOSTNAME was added to resource selection in rank and requirements generator.

Updated by Srinivasan Natarajan over 2 years ago

Changes are made differentiate thin client (gui runs on user machine) and display exporting (gui runs on the machine where gridway is installed) based on LOGINHOST configuration attribute.

Updated by Srinivasan Natarajan over 2 years ago

  • % Done changed from 90 to 100

GTK Themes are added for documenting modules as thin client and exporting of display. Based on various themes snapshots are added to gridway documentation

Updated by José Luis Vázquez Poletti over 2 years ago

  • Status changed from Assigned to Closed

Also available in: Atom PDF