Dear slurm-users, for interested parties, we have dropped another version of goslmailer (v.2.4.0), this time with a discord connector and bot. Now supporting job notifications delivery to discord servers, in addition to already existing ones: matrix, telegram, msteams and e-mail.
As usual, all the information can be found at the project github README: https://github.com/CLIP-HPC/goslmailer best, Petar On Fri, Jul 1, 2022 at 11:27 AM Tomás Di Domenico <td...@tdido.ar> wrote: > Hello everyone. > > For those interested, we've just added a Matrix connector to goslmailer, > which allows slurm to send messages to Matrix rooms. The README file of > the project [1] has details on functionality and features. > > If you do use it, we'd love to hear your feedback! > > Best, > Tomás > > [1] https://github.com/CLIP-HPC/goslmailer > > On 18/05/2022 14:39, Petar Jager wrote: > > > > Hi Hermann, > > > > You're welcome, looking forward to hearing some feedback from you. > > > > Regarding the matrix integration, or any other for that matter, gosl > > code was written with extensibility in mind. > > Meaning, all the helper code required to create a new connector is > > packaged and easily reusable. > > If you take a look at telegram and msteams connectors, you'll see > > they're ~90% boilerplate code with a few lines of system specific api > calls. > > > > That makes the complexity of implementation depend solely on the API of > > the other system and implementers familiarity with it. > > Guessing the time estimate is not simple, depends on a lot of factors. > > For me, never having used the matrix and reading its documentation for > > the first time now, it would be much more than for someone familiar with > > it. > > Together with the test system setup, understanding of the protocol, > > libraries, code, figuring out the preferred workflow, testing, etc.. I'd > > guess a couple of weeks (with my usual load). > > For someone intimately familiar with matrix, probably it's measured in > days. > > > > I'd suggest you open an issue on github with this as a feature request, > > and if you have the resources to start working on the connector > > yourself, we'll be more than happy to assist you getting around, > > or else we'll see if could manage the time on our side to tackle this if > > there is wider interest for this integration. > > > > best, > > Petar > > > > On Tue, May 17, 2022 at 5:31 PM Hermann Schwärzler > > <hermann.schwaerz...@uibk.ac.at <mailto:hermann.schwaerz...@uibk.ac.at>> > > > wrote: > > > > Hi Petar, > > > > thanks for letting us know! > > We will definitely look into this and will get back to you on GitHub > > when technical questions/problems arise. > > > > Just one quick question: we are neither using Telegram nor MS-Teams > > here, but Matrix. In case we would like to deliver messages through > > that: what's your guess on how much work it would be to implement it? > > > > Regards, > > Hermann > > > > On 5/16/22 2:20 PM, Petar Jager wrote: > > > > > > Hello slurm users, > > > > > > we, the Vienna BioCenter HPC team, got a bit carried away and > > developed > > > a slightly elaborate slurm notification solution. > > > > > > It acts as drop-in for regular MailProg mailer and can do: > > > > > > * message delivery to: e-mail (enhanced classic), telegram, > msteams > > > * gathering of job statistics > > > * generating hints for users on how to tune their job scripts > > > * template able messages > > > * message throttling > > > > > > You can find it here: https://github.com/CLIP-HPC/goslmailer > > <https://github.com/CLIP-HPC/goslmailer> > > > <https://github.com/CLIP-HPC/goslmailer > > <https://github.com/CLIP-HPC/goslmailer>> > > > > > > We hope you find it interesting (and helpful) and if you have > > ideas or > > > would like to contribute, feel free to reach out to us there :) > > > > > > > > > best, > > > Petar > > > > > > > > > -- > > > Petar Jager > > > mailto:petar.ja...@gmail.com <mailto:petar.ja...@gmail.com> > > <mailto:petar.ja...@gmail.com <mailto:petar.ja...@gmail.com>> > > > > > > > > -- > > Petar Jager > > mailto:petar.ja...@gmail.com <mailto:petar.ja...@gmail.com> > > -- Petar Jager mailto:petar.ja...@gmail.com
