Re: [HTCondor-users] RPMs vs curl get.condor.org vs tarball

[John M Knoeller <johnkn@xxxxxxxxxxx>]

The tarball builds include things that are RPM dependencies for the RPM builds.   This is one of the differences between the tarball and RPM builds on Linux.

 

The other main difference is that the tarball unpacks everything to a single directory, while the RPM scatters files across the file system into the standard Linux directories /bin, /etc

 

You should be able to use either.  If you have your own RPM repo, then downloading the RPMs is probably easiest.    

 

As for the curl get.htcondor.org instructions,  this basically just pulls down a bash script that drives the RPM install and does a bit of configuration. You can look at the script or execute it with –dry-run to see what commands it would execute.

 

-tj

 

From: HTCondor-users <htcondor-users-bounces@xxxxxxxxxxx> On Behalf Of Sam.Dana@xxxxxxxxxxx
Sent: Thursday, July 27, 2023 7:36 PM
To: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
Subject: [HTCondor-users] RPMs vs curl get.condor.org vs tarball

 

I'm new to HTCondor and need to build a pool in a cluster of multiple Red Hat and Windows machines.

As my cluster is disconnected from the Internet, curl get.condor.org doesn't work for me. 

I grabbed condor-10.0.6-x86_64_CentOS7-stripped.tar.gz and condor-10.0.6-Windows-x64.msi.

The docs mention RPM-based Distributions, which I can setup on as a local repo, but which rpms do I install? 
I see installing condor.*.rpm requires voms from epel, for example. Do the rpms have different requirements for running condor than the tarball I downloaded?

Which should I be using for a basic functional, beginner-level, cluster?

 

The Administrator Quick Start Guide provides "curl get.htcondor.org"-based instructions. How do I translate these into tarball-based (and rpm-based) commands?

 

 

NOTICE: This email message and all attachments transmitted with it may contain privileged and confidential information, and information that is protected by, and proprietary to, Parsons Corporation, and is intended solely for the use of the addressee for the specific purpose set forth in this communication. If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited, and you should delete this message and all copies and backups thereof. The recipient may not further distribute or use any of the information contained herein without the express written authorization of the sender. If you have received this message in error, or if you have any questions regarding the use of the proprietary information contained therein, please contact the sender of this message immediately, and the sender will provide you with further instructions.