Worker Node Client Native Packages
The VDT has put together RPMs for installing a worker node client. They are
derived from our Pacman packages for VDT 2.0.0.
The current set of packages making up the worker node client is:
...plus their dependencies.
These packages are set up similar to our Pacman packages in that they install
, are binary-only (i.e., there are no source RPMs) and you need
to set up your environment before using them. They are a work in progress and
we greatly appreciate any feedback.
For those who like to browse, here is a direct link to the files in the repository
To use these packages you must have a Red Hat Enterprise Linux 5 or compatible
installation (e.g., CentOS 5 or Scientific Linux 5). We have both 32- and
64-bit packages available.
You should not have EPEL repositories enabled while using these packages,
since they provide conflicting packages for some of the grid software we
distribute (e.g., the Globus Toolkit).
Enabling the Repository
As root, do the following:
- Install the VDT repository metadata package:
rpm -Uvh $VDTWWW/native/rpm/repo/vdt-testing-1-1.noarch.rpm
- If they are installed, disable EPEL repositories. Note: DAG and RPMforge repositories do not conflict and may be left enabled.
- Install VDT RPMs*:
yum install PACKAGENAME
- If not already done, install CA certificates.
We have a metapackage named
bring in all of the necessary packages for a worker node client install. To
yum install osg-worker-node-client
In general, all installed files will be placed into the
To run most grid software, you must have CA certificates installed. VDT RPMs
that require CA certificates expect those certificates to be installed in
Before using any of the worker node client tools, you must set the
appropriate environment variables. In the shell you plan to run the tools in,
you must source the setup.sh file by running:
after you log in. If you are running one of the tools as part of a script or
a cron job, you must make sure that the script sources
executing any of the tools.
To remove a specific package, type:
yum erase PACKAGENAME
Yum will remove the package and any packages that depend on it. Note:
Removing a metapackage such as
will not actually uninstall any software,
as the metapackages are just empty packages which have the real software listed
as dependencies. You must remove the individual software you wish to
As a shortcut, we placed most of the osg-worker-node-client packages into a
yum group, meaning that you can run:
yum groupremove osg-worker-node-client
to uninstall most of the worker node client. Not all packages will be
uninstalled, since we have no way of knowing the difference between packages
installed manually and packages brought in as dependencies, and some packages
are used in more
than just the worker node client.
To completely uninstall all VDT RPMs, type:
rpm -e `rpm -qg Applications/Grid`
Do not use these packages in conjunction with:
- EPEL grid packages, especially EPEL Globus packages
- VDT Pacman installations placed in
- VDT Globus 5-based RPMs customized for LIGO
These packages are a work in progress. They've only been minimally tested
and should not be used in production sites. We'd greatly appreciate feedback,
especially on the following topics:
- Do the packages function the way you expect them to?
- Can you use the packages in a small test environment? Can you connect to a remote server, transfer files, and run jobs?
- Is the default configuration provided appropriate for your needs?
- What kinds of problems have you run into while using the packages?
- What changes do you need before you're willing the use the packages in production?