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

[Tim Theisen <tim@xxxxxxxxxxx>]

Hello,

The tarballs are generally used to personal condors (one that an unprivileged user run within their home directory). The tarballs contain all the dependencies that are not on a typical Red Hat system.

The packaged versions are generally used by system administrators. They include integration with the system (systemd files, automatically setup the appropriate log directories etc.).

It is highly recommended to use the packaged versions if you are the system administrator.

The gethtcondor shell script could be run on a machine that has access to the internet and you could observe which packages are downloaded. You could them compare this list of package with the output of 'rpm -q' on your Red Hat system to see what packages are needed. You could then download them and their public keys and set up your own locker repository.

One could set up a system using the tarball as root. However, we don't even document how to do this.

By default, the gethtcondor shell script, does a dry run, so that you can observe the steps that it takes.

There are several articles on the internet on how to setup local repositories for air-gapped systems.

I hope you find this helpful. Feel free to ask further questions.

...Tim

    On 7/27/23 19:36, Sam.Dana@xxxxxxxxxxx wrote:

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.

_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/

-- 
Tim Theisen (he, him, his)
Release Manager
HTCondor & Open Science Grid
Center for High Throughput Computing
Department of Computer Sciences
University of Wisconsin - Madison
4261 Computer Sciences and Statistics
1210 W Dayton St
Madison, WI 53706-1685
+1 608 265 5736