Monday, September 22, 2008

Nightly Build Update

The "portal only" release was upgraded to Tomcat 5.5.27, but the build and test scripts on the NMI testbed were still set to use the older Tomcat 5.5.12. This has been corrected.

For more info on the nightly build, see

Nightly Builds OK

There is a bug in the NMI nightly build scripts that prevents Tomcat from starting. This causes the build to report a failure, but the compilation steps complete successfully.

Friday, September 12, 2008

Tagged Update to GTLAB

Numerous improvements and bug fixes to the GTLAB tag libraries have been tagged as "GTLAB-2008". These supersede the TG08 tagged version. To get the updates, use

svn checkout

Major changes include
  • Bug the prevented task inter-dependencies from working correctly has been fixed.
  • Each GTLAB tag can now be associated with its own resource property file. Previously all tags used the same property file.

Tagged Preview of OGCE portal 2.4

The OGCE "portal only" release has been tagged as a preview. This version includes numerous bug fixes and updates. To get it, use

svn checkout

Most updates are courtesy of Lukas Hoffman.


* Edited files: portlets/gp-common/src/main/webapp/css/fileBrowser.css
* This isn't really a portlet, it just contains files that are used by the GridPort portlets

Interactive Job Submission / jobsubmit-portlet

* Edited files: portlets/jobsubmit-portlet/src/main/webapp/templates/xportlets-jobsubmit.vm
* Added *'s for certain fields in the job submission form & a note saying those fields were required.
* Added a way to link to standard output and standard error files
* Added help instructions in "?" viewing window
* If user left stdout/stderr field blank, job output is displayed in portlet when job completes. see 'lukas code' where stdout is mentioned in and xportlets-jobsubmit.vm
* If user enters path from root to stdout/stderr, there's a link to download the file. This is glitchy though, it only works if filetransfer portlet is connected to correct host, and it doesn't work for relative paths.

File Manager/file-manager and Comprehensive File Management/comp-file-management

* Edited files: portlets/comp-file-management/src/main/webapp/jsp/fileBrowser.jsp
portlets/gp-common/src/main/webapp/jsp/fileBrowser.jsp - identical to fileBrowser.jsp above
* Added an image href to the file/directory listing
* Files are now sortable by name, filetype, and size. Default is sort by filetype. User can click on a heading to select a sort.
If user clicks on a heading twice in a row, the sort is in reverse order.
* Refresh button went to home directory, now it's refresh current directory.
* Fixed something in but I forgot what the problem was.
destListing.setRemoteHost(destResources[0]); //lukas code, previous array size = 1 --> this portlet crashes.
//don't know why this fix works, but it works...

File Transfer Portlet / GridFTP Portlet / filetransfer (Deprecated)

Edited files: portlets/filetransfer/src/main/webapp/gridftp-browser.vm
* is all my own code, so the directory contains a javadoc html page for this class
* fixed bug where file download & file transfer don't work if filenames contain spaces.
* fixed bug where clicking on a link twice really fast made portlet crash
* fixed two or three "annoying but not fatal" bugs that I don't remember now, although I probably wrote that it was a fix in the source code comments
* Added a "Type" (Filetype field) so the file list matches the information that any Windows directory listing gives you
* Made the "Date Modified" dates look better
* Files/Directories are now sortable by Name, Size, Type, and Date Modified. They stay sorted that way until the user clicks on a heading.
* Sorting is in reverse order when user clicks a heading twice.
* Made icons and file/directory names clickable, for easier access with the mouse. Before, the link to download a file was on one side & the
file name was on the other, which is annoying for the user. Now the user can click directly on the file name or icon to download it, or
directory name/icon to go there.
* Moved things around to make portlet look better. Mostly, moved all buttons and links toward the top and put file listing under them.
* User can now
make a new directory
rename a file/directory
delete 1 or more files at a time
delete a directory
go to any directory in 1 step by typing in the full path name, or path name relative to current directory, or ".." to go up a directory
(typing "dir1/dir2/dir3" and pressing submit is faster than clicking 3 links)
* Added error messages when the commands above fail & display to the user.
* Added help instructions in "?" viewing window
* Luke Hammill fixed problem where if you accidentally transfer a file to itself (same action as: mv fileA fileA) file gets deleted. (fix not in version i sent you)
* back.gif button can now go to '/', which it couldn't before.
* 'Home' link now always goes to directory that showed up when the host was first loaded, which it didn't before.
* You can delete several files at a time using checkboxes.

Wednesday, September 10, 2008

GCE08 Submission Deadline Extension

The deadline for submitting papers to GCE 08 has been extended to September 22. See for more information.

Monday, September 08, 2008

Condor Installation Example

The following is an example installation for Condor 6.8.8. This is required to use the Condor and Condor-G portlets. Additional configuration is required to enable Birdbath and Condor-G, so see the portlet notes at

Note also that this version of Condor will not work on newer RHEL and Fedora releases, so you will need to get the library. Do the following as root:

[shell> yum install

Now do the following in the condor-6.8.8 release directory.

[shell> condor_install

Press enter to begin Condor installation

STEP 1: What type of Condor installation do you want?

Would you like to do a full installation of Condor? [yes]

Press enter to continue.

STEP 2: How many machines are you setting up for Condor?

Are you planning to setup Condor on multiple machines? [yes] no

Press enter to continue.

STEP 3: Install the Condor "release directory", which holds
various binaries, libraries, scripts and files used by Condor.

It looks like you've installed a Condor release directory in:
Do you want to use this release directory? [yes] no

Have you installed a release directory already? [no] no

Where would you like to install the Condor release directory?
That directory doesn't exist, should I create it now? [yes]
Installing a release directory into /home/mpierce/condor ...

[------------------------------Stuff deleted------------------------------]


Using /home/mpierce/condor as the Condor release directory.

Press enter to continue.

STEP 4: How and where should Condor send email if things go wrong?

If something goes wrong with Condor, who should get email about it?

What is the full path to a mail program that understands "-s" means
you want to specify a subject? [/bin/mail]

Using /bin/mail to send email to

Press enter to continue.

STEP 5: Filesystem and UID domains.

To correctly run all jobs in your pool, including ones that aren't relinked
for Condor, you must tell Condor if you have a shared filesystem, and if
so, what machines share it.

Please read the "Configuring Condor" section of the Administrator's manual
(in particular, the section "Shared Filesystem Config File Entries")
for a complete explaination of these (and other, related) settings.

Do all of the machines in your pool from your domain ("")
share a common filesystem? [no]

Configuring each machine to be in its own filesystem domain.

Do all of the users across all the machines in your domain have a unique
UID (in other words, do they all share a common passwd file)? [no]

Configuring each machine to be in its own uid domain.

Press enter to continue.

STEP 6: Java Universe support in Condor.

Enable Java Universe support? [yes] no
OK, Java Universe will be left unconfigured.

Press enter to continue.

STEP 7: Where should public programs be installed?

The Condor binaries and scripts are already installed in:
If you want, I can create some soft links from a directory that is already
in the default PATH to point to these binaries, so that Condor users do not
have to change their PATH. Alternatively, I can leave them where they are
and Condor users will have to add /home/mpierce/condor/bin
to their PATH or explicitly use a full pathname to access the Condor tools.

Shall I create links in some other directory? [yes] no

Press enter to continue.

STEP 8: What machine will be your central manager?

What is the full hostname of the central manager?

Your central manager will be on the local machine.

Press enter to continue.

STEP 9: Where will the "local directory" go?

Condor will need to create a few directories for its own use

You have a "condor" user on this machine. Do you want to put all the
Condor directories in /home/condor? [yes] no

Do you want to put all the Condor directories in
/home/mpierce/condor/home? [yes]

Creating all necessary Condor directories ... done.

Press enter to continue.

STEP 10: Where will the local (machine-specific) config files go?

Condor allows you to have a machine-specific config file that overrides
settings in the global config file.

You must specify a machine-specific config file.

Should I put a "condor_config.local" file in /home/mpierce/condor/home?
Creating config files in "/home/mpierce/condor/home" ... done.

Configuring global condor config file ... done.
Created /home/mpierce/condor/etc/condor_config.

Press enter to continue.

Setting up as your central manager

What name would you like to use for this pool? This should be a
short description (20 characters or so) that describes your site.
For example, the name for the UW-Madison Computer Science Condor
Pool is: "UW-Madison CS". This value is stored in your central
manager's local config file as "COLLECTOR_NAME", if you decide to
change it later. (This shouldn't include any " marks).

Setting up central manager config file /home/mpierce/condor/home/condor_config.local ... done.

Press enter to continue.

STEP 11: How do you want Condor to find its config file?

Condor searches a few locations to find it main config file. The first place
is the envionment variable CONDOR_CONFIG. The second place it searches is
/etc/condor/condor_config, and the third place is ~condor/condor_config.
/home/condor/condor_config exists.
Renaming to: /home/condor/condor_config.old.

Should I put in a soft link from /home/condor/condor_config to
/home/mpierce/condor/etc/condor_config [yes]

Press enter to continue.

Condor has been fully installed on this machine.

/home/mpierce/condor/sbin contains various administrative tools.
If you are going to administer Condor, you should probably place that
directory in your PATH.

To start Condor on any machine, just execute:

Since this is your central manager, you should start Condor here first.

Press enter to continue.

You should probably setup your machines to start Condor automatically at
boot time. If your machine uses System-V style init scripts, look in
for a script that you can use to start and stop Condor.

Please read the "Condor is installed... now what?" section of the INSTALL
file for things you should do before and after starting the Condor daemons.
In particular, you might want to set up host/ip access security. See the
Adminstrator's Manual for details.