Wang, Fugang: Progress Report

* Legend *

[] Planned

[X] Completed

[*] In progress (might span to several weeks)

[?] Open questions/discussions.

-----------------------------------------------------------

Long Term Goals

  • [] Finish the JavaScript API library for Grid computing.
  • [] Construct a web2.0 based portal based on 1.
  • [] Deliver document and code and summarize the work into a thesis.

Tasks for SC09

  • [X] Fix current issues and improve code.
  • [X] Simplify imstallation and configuration of the system.
  • [X] Construct Web Gadgets version of the system.
  • [*] More stable release as well as demo.

Fall 2009

Week Nov 16 - Nov 21

  • [] SC09 conference.

Week Nov 9 - Nov 15

  • [X] File listing timeout setup.
  • [X] Job highlight in history list when displaying its result/output.
  • [*] Some other fixes/improvements.
  • [*] Unified version of Cyberaide JavaScript API.
  • [] Prepare presentation/demo for SC09.

Week Nov 2 - Nov 8

  • [X] Completed the file browser/transfer gadget.
  • [X] Worked on style settings of gadgets for better view.
  • [X] Added SSL site cert noticement if the libraries were not loaded properly for first time use.
  • [X] Error report panel added to the gadgets.

Week Oct 26 - Nov 1

  • [X] Finish Job management gadget functionality.
    • Due to the difficulty to get csv datastore from dojo working, had to give up this approach.
    • Fetch tg info directly from the tg site and process it to get wsgram and gridftp list.
    • Mvn build issue. Be cautious if mvn has been installed prior the build.
    • UID negative number issue occured and was fixed.
  • [X] work on file transfer gadget.
  • [] Myproxy info and logout feature.

Week Oct 19 - Oct 25

  • [*] Job management gadget is partialy ready. Dojo is not working. Need to figure out a solution or replace it with other means.
    • when loading dojo from a self-maintained server, the csv datastore was unable to be loaded.
    • when loading it from an outside site like googleapi, all the components could be loaded, but the datastore url could not be specified to another site (a violation of same-origin policy)
  • [] myproxy info and destroy feature.

Week Oct 12 - Oct 18

  • [X] Fix/improve installation script if necessary.
  • [X] Worked on the error/log message reporting framework in client side.
  • [X] Added error report during job/workflow execution.
  • [*] Try to get the job management gadget working; or idendify problems/obstacles if there is any.
    • [X] A bunch of tests/trials of the tabbed gadget. Get the UI working in iGoogle.
    • [X] Add/Debug the scripts code that communicates with backend services.

Week Oct 5 - Oct 11

  • [X] Replaced the old jGlobus with the latest 1.7.0 version, so it can do trusted root CA bootstrap.
  • [X] By solving the CA and myproxy issues, now Globus has been eliminated from the dependency list.
  • [X] Improve the install script/fix issues to accomodate both Linux and Mac OS systems. Tested on iris01 at RIT(OSX), gf17 at IU(centos), and locally in Ubuntu.
  • [*] Working on converting job management related icons/windows into google gadget.

Week Sept 28 - Oct 4

  • [*] Explore MyProxy from jGlobus 1.7.0. to eliminate the dependency on Globus Toolkit installation
  • [X] Bundle Java CoG installation instead of using the cog-setup GUI for installation, thus make deploying on remote machine a possibility.
  • [X] More test on both locally and remotely on IU's GF machines.

Week Sept 21 - Sept 27

  • [*?] When testing with deployment into one single machine without globus installation, myproxy will encounter error when retrieving certiificates. Using newer version jGlobus with CA bootstrapping issue fixed may resolve this.
  • [X] Replaced globus-url-copy from Globus with cog-file-transfer from CoG, to deal with file transfer. This is the first step to eliminate the dependency on Globus Toolkit.
    • Changed server side FileTransfer code and client side code relating to file listing, transfer
  • [X] Streamline of installation with a shell script, assuming deploy on one single host.
    • Autodownloading and installation of Maven2, Java CoG, Tomcat; skip downloading of local copy of installation packet found. These make Java 6 the only prerequisite part that have to be dealt with externally by user.
    • Covered bunch of test cases. More would be done along with further improvement.
  • [*] Investigate/test alternative karajan workflow for directory listing.
    • the new script will get the redirected output synchronously(blocked) in the service side. So if it will be used, a new schema to deal with this need to be implemented, instead of reusing the current asynchronous schema: "submit request as a job" -> "check status" -> "get result"
    • Woud this be worth the effort?
  • [*] Think about mechanisms to report error/log from server side to client side while invoking functions.
    • using a message system to report the error/log? Apache ActiveMQ would be a good choice. The error would be push into the JMS, and the Ajax feature of the ActiveMQ will support message pushing to JavaScript client.
    • Is this too heavy?

Week Sept 14 - Sept 20

  • [X] Fixed some issues on the client side code, including Gram resource endpoint name, gridftp resource endpoint name, and job submission hostname initialization.
  • [] Get start with some experiment/test for the cyberaide gadget transformation.
  • [X] Fininalize Agent server one-step installation.

Week Sept 07 - Sept 13

  • [X] CXF-Servlet replaced Axis2 as the SOAP engine for Agent service, fixing the memory build up issue as well as simplying dependencies and configuration.
  • [X] Fixed the UID generation issue, as well as did some other minor changes.
  • [X] Tomcat and presetted configurations pre-packaged into the installation packet.
    • [X] Study installation and deployment tricks used in OGCE.
    • [X] Include Tomcat into installation package. Or retrieve the package using wget/curl during installation.
    • [X] Use pre-configurated config files for Tomcat. Possible port # change to avoid possible confliction with existing Tomcat instance.
  • [X] Modify installation script to simplify Agent server side installation into one step ( (Download? and) Install Tomcat; configuration with preset config files; compile Agent code and package into war; deploy the war; deploy client code).
  • [?] Should we, and how could we automate the HTTPS configuration, since that needs user's interaction for the cert's info.
  • [*] Research more on the Gadget transformation.
    • [*] Study documents from google gadgets site.
    • [X] Think about the gadget approach. A preliminary thought: Before we figure out the solution for one-icon-one-gadget, or find out that is not an appropriate way, we could first develop gadgets based on functionality groups. For example, one for Info Services; one for job management; one for file transfer. Some gadget would include several 'icons' implemented using the 'tabs' feature from gadget. In this way, the job management gadget and file transfer gadget will both have a tab for myproxy authentication.

 

--------------------------------------------------------------------------------------------------------------------------

Archived Activities Report:

--------------------------------------------------------------------------------------------------------------------------

Before 2009 Fall