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

[Brian Andrus]

I've definitely been there with the minimum cost issue. One thing I have 
done personally is start attending SLUG. Now I can give back and learn 
more in the process. That may be an option to pitch, iterating the value 
you receive from open source software as part of the ROI.

Interestingly, I have been able to deploy completely to cloud using only 
slurm. It has the ability to integrate into any cloud cli, so nothing 
else has been needed. Just for the heck of it, I am thinking of 
integrating it into Terraform, although not necessary.

Brian Andrus

On 1/26/2021 11:48 AM, Robert Kudyba wrote:
>
>
> On Mon, Jan 25, 2021 at 6:36 PM Brian Andrus <toomuchit at gmail.com 
> <mailto: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?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.schedmd.com/pipermail/slurm-users/attachments/20210127/9f941b78/attachment.htm>