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

Re: [HTCondor-users] condor_ssh_to_job

On Thu, Aug 22, 2013 at 2:05 PM, Todd Tannenbaum <tannenba@xxxxxxxxxxx> wrote:
> Wish there was a way to do this via an RPM/Deb install without having to
> prompt the user for a range; if anyone has ideas, please share!

This is by no means a *good* idea, but you didn't ask for good ideas...
One possibility is to detect the number of CPU cores during the post
installation step and create that number of slot users. This ends up
with too many users (meh) when there are fewer slots than cores and
too few users (this is a problem) when there are more slots than cores
(but if you're doing this, you can probably create your own additional

On Thu, Aug 22, 2013 at 2:41 PM, Rich Pieri <ratinox@xxxxxxx> wrote:
> Don't do it directly from the packages. Do it from a configuration tool
> invoked as part of the post-install process.

It depends on what you mean by post-install. If you mean as a step in
the $packagemanager installation process, this is a non-starter for
RPM-based systems because RPM doesn't do interactive installation. If
you mean "first run $packagemanager, then run the scripts", that would
work, but it doesn't scale well.

Of course, at scale the "right" way to do it is probably for the admin
to define the users in the configuration management tool being used,
but we can't rely on people to use configuration management (it hurts
me to have to type that).

Another possible solution is to create a single slot user that all
slots will use and include this admonition that "this is really not a
great idea. Create more users as needed."

Ben Cotton
Senior Support Engineer
Cycle Computing, LLC
The Leader in Utility Supercomputing Software