Hi Riccardo, PR #167 can be deleted - it's a subset of PR #168.
The cluster start/stop has been working very reliably (though I continue to struggle with getting some version of Ansible to complete the Slurm configuration), so I think PR # 168 is ready to merge. I will continue to test until I get success with Ansible, just for my own peace of mind. But the Azure provider itself should not be affected. Regards, Dave On Wed, Oct 5, 2016 at 12:23 PM, Riccardo Murri <[email protected]> wrote: > Dear Dave, > > > I've updated the branch on bobd00 containing the PR for adding azure. See > > https://github.com/bobd00/elasticluster/blob/azure_ > support_part2/README-AZURE.rst > > > > Still testing the Slurm issue noted below, but I wanted to get this out > > there for testing in the meantime. > > So can I merge PR #167 and #168 or should I wait for more updates? > > Ciao, > R > > -- > Riccardo Murri, Schwerzenbacherstrasse 2, CH-8606 Nänikon, Switzerland > -- 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.
