[slurm-users] Exclude Slurm packages from the EPEL yum repository

[Loris Bennett]

Same here - $10k for less than 200 nodes.  That's an order of magnitude
which makes the finance people ask what we are getting for the money.
As we don't have any special requirements which would require
customisation, that's not easy to answer, so currently we don't have a
support contract.  However, I feel we should really contribute to
SchedMD's continued existence.

Cheers,

Loris
 

Jason Simms <simmsj at lafayette.edu> writes:

> We’re in the same boat. Extremely small cluster. $10k for support. We
> don’t need nearly that level of engagement, but there ya go. We’ve
> passed for now, but I’d like to have a support contract ideally.
>
> Jason
>
> On Tue, Jan 26, 2021 at 2:49 PM Robert Kudyba <rkudyba at fordham.edu> wrote:
>
>  On Mon, Jan 25, 2021 at 6:36 PM Brian Andrus <toomuchit at gmail.com> wrote:
>
>  Also, a plug for support contracts. I have been doing slurm for a very 
>  long while, but always encourage my clients to get a support contract. 
>  That is how SchedMD stays alive and we are able to have such a good 
>  piece of software. I see the cloud providers starting to build tools 
>  that will eventually obsolesce slurm for the cloud. I worry that there 
>  won't be enough paying customers for Tim to keep things running as well 
>  as he has. I'm pretty sure most folks that use slurm for any period of 
>  time has received more value that a small support contract would be.
>
>  We considered this but we have a very small cluster. And when I reached out for a quote, I was told "SchedMD has a MIN node count of 256 for $10K/yr".
>
>  Since we're using Bright Computing we've always had to ignore Slurm updates from yum and have to compile our own version.
>
>  Curious, which cloud provider scheduling tools do you see gaining traction?
-- 
Dr. Loris Bennett (Hr./Mr.)
ZEDAT, Freie Universität Berlin         Email loris.bennett at fu-berlin.de