Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] HTCondor 23.0.24, 23.10.24, 24.0.7, and 24.7.3 Released
- Date: Fri, 25 Apr 2025 14:16:20 -0500
- From: Greg Thain <gthain@xxxxxxxxxxx>
- Subject: Re: [HTCondor-users] HTCondor 23.0.24, 23.10.24, 24.0.7, and 24.7.3 Released
On 4/25/25 02:28, Thomas Hartmann wrote:
But seeing the announcement, I would be curious about your
experiences, and if shaping IPAddress{Allow,Deny} drop-ins for all the
Condor units would be the way to go for an admin or maybe if an
extension of the network control within the job namespaces would be a
reasonable idea? I.e., Condor knobs for admins to control which IP
ranges daemons or starters are allowed/denied to talk to?
Hi Thomas:
Interesting ideas -- the use case we had in mind here was glidein, where
an administrator is willing to let a glided-in condor use the network to
fetch the job, report status, etc., but they don't want the job to use
any of the bandwidth. Perhaps the bandwidth at the site is very
limited. I suspect setting a deny list might be better security, but
harder to maintain over time?
-greg