[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] Condor package for OSCAR!

Hi Amit,

Not sure if this will help you on your mission, but I have written a
spec file that we use here at our site. No sense in duplicating work.

Here are our basic instructions:
  1.  Copy either
     based on the systems achitecture.
  2. Put the Condor Spec File as /usr/src/redhat/SPECS/condor.spec
  3. In /usr/src/redhat/SPECS type rpmbuild -ba --define "cversion
$VERSION" condor.spec

   * Replace $VERSION with the condor version, such as 6.8.5 This has
been tested with 6.8 and 6.9 versions.

Verify the build with, for example:

rpm -qlp /usr/src/redhat/RPMS/i386/condor-6.8.5-1.LIGO.i386.rpm

I have a lot of experience with condor spec files, so if you write a
basic "script" to define submit nodes or compute nodes, I can modify
my spec and have a condor-submit/condor-compute package that will
include init scripts and condor config files.


On 7/18/07, Amit Vyas <amitvyas.cse@xxxxxxxxx> wrote:
Hi all,

I am developing a Condor package[1]  for OSCAR[2] as part of Google Summers
of Code [3][4],

For those who don't know OSCAR, "it is a software for installing and
managing Beowulf type HPC cluster , where it has one HeadNode and all other
client machines which are installed by headnode and required softwares are
installed onto them"

Condor package will provide condor installation/configuration to happen on
headnode and clients.
Since there are many advanced configuration condor can take through
condor_config I have settled down for most basic of it which can be deployed
and can make a cluster ready for condor jobs.

A look at [5] will tell Condor can be configured as follows on a Oscar
cluster( please know that /home is shared by all cluster machines)

1. Condor will install as manager and submit node at headnode
 2. It will be installed as execute mode at all clients.
3. it will create a condor service to automatically start condor at reboot.
4. Can create condor user for cluster.
5. Change config file for Flocking to and from other pools( all client nodes
remain in private network generally)
6. Can also allow headnode to be a execute node(for small cluster, or
testing purpose)

installation happens through rpms , and on all machines  local-dir is

 My intentions for this mail are to collect question,feedback, suggestions,
advices on this so that I can try to do  some  improvements fro 1st release
so that it can suit to large condor users/admins , and can learn from
experience condor users.


[2] http://oscar.openclustergroup.org/
[4] http://code.google.com/soc
Amit Vyas
Condor-users mailing list
To unsubscribe, send a message to
condor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting

The archives can be found at:

Attachment: condor.spec
Description: Binary data