HI Julien, thanks for replying! I am glad to see you're still using ElastiCluster :-)
> My preference would be to make everything opt-in, as deployment times > matter, and external bandwidth can cost money in some cases. I tend to lean on the "all inclusive" side, as both deployment times and bandwidth are non-issues here, but I can see they can be pain points elsewhere. What do others think? I am definitely open to a more "opt-in" approach, as long as it does not go too much in the way of the common use cases at UZH. > I already found myself having to edit the elasticluster playbooks to > disable some stuff (selinux, pdsh IIRC). I can see how you can make PDSH an optional package, but SELinux? AFAICT, it comes by default with CentOS and all ElastiCluster does is trying to work around it... (Do you mean instead that you just do `setenforce 0` at the beginning and forget about it?) > But it is really nice to have package bundles available as playbooks you > can easily enable, so IMHO the only thing missing is documentation ? I > would expect the Python/R/OpenMPI "bundles" to appear in this page: > http://elasticluster.readthedocs.io/en/latest/playbooks.html Good idea, I'll try to split that page into "fundamental" playbooks and "add-on" ones. Ciao, R -- Riccardo Murri / Email: [email protected] / Tel.: +41 77 458 98 32 -- You received this message because you are subscribed to the Google Groups "elasticluster" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
