just to jump on the wagon, we would prefer a postgres option as well. i can't "Create, debug and contribute back" a plugin, but i could help in some fashion
On Sun, Mar 20, 2016 at 5:41 PM, Simpson Lachlan <[email protected]> wrote: > I think we would like a PostgreSQL plugin too - if you start building one, > please let me know so I can contribute. > > Cheers > L. > >> -----Original Message----- >> From: Chris Samuel [mailto:[email protected]] >> Sent: Saturday, 19 March 2016 2:00 PM >> To: slurm-dev >> Subject: [slurm-dev] Re: Regards Postgres Plugin for SLURM >> >> >> On Fri, 18 Mar 2016 06:53:38 AM Doguparthi, Subramanyam wrote: >> >> > We are from Hewlett Packard Enterprise and evaluating >> > SLURM for one of our requirements. Database our application uses is >> > Postgres and we don’t see any working plugin available. Is it possible >> > to help us with Postgres DB plug in? We are ok to add any missing >> > functionality and submit back the changes. >> >> PostgreSQL support was removed in the 14.03 release two years ago. >> >> The release notes said: >> >> -- Support for Postgres database has long since been out of date and >> problematic, so it has been removed entirely. If you would like to >> use it the code still exists in <= 2.6, but will not be included in >> this and future versions of the code. >> >> The RPM you've found is from Slurm 2.3.x, which is ancient. >> >> So I suspect there are 3 options: >> >> 1) Use Slurm 2.6.x (which is no longer maintained) >> 2) Use MySQL instead of PostgreSQL for Slurm >> 3) Create, debug and contribute back an out of tree, fully functional >> PostgreSQL >> plugin & see what folks think. >> >> All the best, >> Chris >> -- >> Christopher Samuel Senior Systems Administrator >> VLSCI - Victorian Life Sciences Computation Initiative >> Email: [email protected] Phone: +61 (0)3 903 55545 >> http://www.vlsci.org.au/ http://twitter.com/vlsci > This email (including any attachments or links) may contain > confidential and/or legally privileged information and is > intended only to be read or used by the addressee. If you > are not the intended addressee, any use, distribution, > disclosure or copying of this email is strictly > prohibited. > Confidentiality and legal privilege attached to this email > (including any attachments) are not waived or lost by > reason of its mistaken delivery to you. > If you have received this email in error, please delete it > and notify us immediately by telephone or email. Peter > MacCallum Cancer Centre provides no guarantee that this > transmission is free of virus or that it has not been > intercepted or altered and will not be liable for any delay > in its receipt. >
