Status Report for 12/21/06 to 12/27/06

I've installed CEMon Client APIs in my local machine. The following is my summary of CEMon Client API installation.
1. Download the most recent files from http://grid.pd.infn.it/cemon/ClientRPMs
2. Install RPMs as follow:
rpm -ivh c-ares-1.3.0-1.slc3.i686.rpm
rpm -ivh glite-security-gsoap-plugin-1.4.0-0_U200612071426.i386.rpm
rpm -ivh gpt-VDT1.2.2rh9-1.i386.rpm
rpm -ivh glite-security-gsoap-plugin-1.4.0-0_U200612071426.i386.rpm
rpm -ivh glite-ce-monitor-client-api-c-1.7.5-0_U200612071517.i386.rpm
3. Set up library path:
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/glite/lib:/opt/globus/lib:/opt/c-ares/lib
4. Testing
cd /opt/glite/bin
CEMonitorGetInfo

Although I haven't completed verifying that CEMon Client APIs are working in my environments, I'm looking at how CEMon is working in client side.

Status Report for 12/13/06 to 12/20/06

Basically CEMon is used to provide/get information for helping resource selection. The service consists of two parts: a CEMon server and a client. While the CEMon server produces information and publishes to its subscribers, the CEMon client consumes the events. CEMon is based on a web service providing WSDL and SOAP message is needed for subscription.

To implement CEMon as a web client using OGCE, I need to do the followings:

1. Install CEMon command line tools and try to use them to know how CEMon service is working
2. Analyze CEMon’s WSDL to find commands between CEMon server and clients
3. Implement CEMon web client by using Java

Now I’m ready to submit a job to OSG since I got a valid certificate and registered a member of OSG VO. For the next week, I will complete step 1.

Status Report for 12/06/06 to 12/12/06

Currently I’m playing around OSG and reading some documents about CEMon. Especially, I found that the following website is useful: http://vdt.cs.wisc.edu/components/cemon.html. After understanding CEMon, I’m planning to build a dashboard portlet which can work with CEMon.

Status Report for 11/22/06 to 11/28/06

1. OGCE portlets
I’m still updating source codes of MEME portlets and Jobqueue portlets by adding comments and removing debugging messages. The source codes and war files will be exported to the SourceForge repository. The following portlets will be added:
a. memejob-portlet : A portlet for MEME job execution
b. moab-dashboard : A portlet for job queue status query
c. serialjob-portlet : A general portlet to execute a series of jobs

2. Open Science Grid
Meanwhile waiting for a user certificate from OSG CA, I’m working on setting up OSG client in my local machine. I think my installation was successful but $VDT_LOCATION/post-install/README reports a few warnings I should fix. I will clear up those as soon as possible and start to look at OGCE in OSG and CEMon.

Status Report for 11/15/06 to 11/21/06

1. Open Science Grid
After coming back Supercomputing '06 at Tampa, I'm looking around Open Science Grid (OSG) to verify whether OGCE portal can also work with OSG environments. For this test, I’ve installed OSG client by following the client installation instructions and been trying to setup correct configuration which includes certificates for GSI settings.

2. OGCE portlets
I’m preparing to export source codes of MEME and job queue portlets to CVS repository by adding comments into the codes and removing verbose debugging messages.

Status Report for 11/1/06 to 11/7/06

During the last week, I was working on Big Red portal by customizing for Supercomputing 06 and updating key portlets such as MEME job submission portlet and MOAB job queue portlets. Major works on portlets are as follows

1. MEME job submission portlet
a. File downloading: Basically, in portlets, file downloading feature is not working well since html header cannot be set by portlets but, instead, portlet container usually control html header such as "Content type" or "Content-Disposition". Thus, using servlet than portlet is more ideal in this situation. Good news here is that servlet and portlet can share data by using session. Thus, I created a servlet for file downloading which can get proxy information for authorization by using shared session.
b. Output retrieval: Outputs executed by a job managers can be retrieved later by using job handler which is an URL string starting with "http" or "https". Under the hood of this function, GASS server is in charge to save data and hand it over to the client upon request.

2. MOAB job queue viewer

a. Job query belongs to the user: Since each machine in Teragrid has different user map file on user certificate, username(id) can be different system by system even in using the same certificate. Simply, we can submit a GRAM job before starting query to get back a correct username by executing “whoami” command. Later, I’m planning to maintain information service to map usernames on different machines file by using RDF and Jena from HP labs.

Status Report for 10/25/06 to 10/31/06

1. Introduction - A Big Red portal development project
The mission is to create portlets for Big Red portal which will be open to the public for those who want to use newly installed supercomputer in IU, Big Red. Most of portlets come directly from OGCE Grid portlets and a few portlets should be created to deal with Big Red's special needs. Currently the following portles are under development:
a. MEME job submission portlet : a portlet to execute a remote MEME command
b. Job status dashboard : a portlet to query job queues managed by MOAB job queue manager
c. IFrame for IU's Knowledge Base : a iframe portlet displaying IU's Knowlege Base webpages.

2. Week activity (10/25 ~ 10/31)
a. Datafile uploading in MEME portlet
-. Datafile uploading function is done.
-. Output downloading will be implemented soon

b. Job queue forecast image portlet

-. A fixed image can be refreshed continually in a specific interval (60 seconds or so).

c. MOAB dashboard

-. A radio button is added to specify a query condition. It can show all jobs or only user's jobs.


3. Next activity
a. Downloading functionality will be implemented in MEME job submission portlet. Then, users can download output directly from the same portlet
b. Job submission portlet enhancement : Adding a "Serial Job" and a "Parallel Job" portlet. A portlet will rather be more general in a way the portlet can be included in OGCE.