Re: [Beowulf] more automatic building

On 29/09/16 00:34, Mikhail Kuzminsky wrote: > I worked always w/very small HPC clusters and built them manually > (each server). But what is reasonable to do for clusters containing > some tens or hundred of nodes ? As Tim and Craig have mentioned there are lots of ways to deal with this, we use

Re: [Beowulf] User notification of new software on the cluster

Hi John, On 28/09/16 09:55, John Hanks wrote: > We take the approach that our cluster is "community managed" and discuss > all aspects of managing it, software installs, problems, usage, > scheduling, etc., in a dedicated slack.com instance > for our center. A really interesti

Re: [Beowulf] more automatic building

I agree with Tim. We are finishing up an Ansible install and it has worked well for us. Initially, we used it internally to help standardize our cluster builds, but is has many more uses. We recently used it to provision a VM that we saved off and uploaded to Amazon for building an AMI. You c

Re: [Beowulf] more automatic building

Any number of approaches will work. When I used to do this years ago (I've long since passed on the technical side) I'd PXE boot, partition the hard disk and set up a provisioning network and base OS install using the Debian FAI (Fully Automated Install) system, and then use cfengine to configu

[Beowulf] more automatic building

I worked always w/very small HPC clusters and built them manually (each server). But what is reasonable to do for clusters  containing some tens or hundred of nodes ? Of course w/modern Xeon (or Xeon Phi KNL) and IB EDR, during the next year for example. There are some automatic systems like O

Re: [Beowulf] User notification of new software on the cluster

Hi, Rob. We do motd and a user newsletter. I really like the cron job and subscribed notification idea. It would interesting to go beyond email, maybe with a subscribable push notification API, something like Pushover. Cheers. On Tue 09/27/16 04:02PM EDT, Rob Taylor wrote: > I wanted to as