Re: [easybuild] Workload managers support

2017-03-14 Thread Xavier Besseron
half of Kenneth Hoste < > kenneth.ho...@ugent.be> > *Reply-To: *"easybuild@lists.ugent.be" <easybuild@lists.ugent.be> > *Date: *Sunday 12 March 2017 at 09:29 > *To: *"easybuild@lists.ugent.be" <easybuild@lists.ugent.be> > *Subject: *Re: [easybuil

Re: [easybuild] Workload managers support

2017-03-13 Thread Alvarez, Damian
;easybuild@lists.ugent.be> Date: Sunday 12 March 2017 at 09:29 To: "easybuild@lists.ugent.be" <easybuild@lists.ugent.be> Subject: Re: [easybuild] Workload managers support * The launcher/bootstrap values also de

Re: [easybuild] Workload managers support

2017-03-12 Thread Kenneth Hoste
Hi Jordi, This looks reasonable to start with indeed. Two more than things that came to mind: * You'll need to distinguish clearly between --resource-manager* and --job*, although that is mostly an issue for the documentation, I guess * The launcher/bootstrap values also depend on which MPI

Re: [easybuild] Workload managers support

2017-03-09 Thread Kenneth Hoste
Hi Jordi, On 09/03/2017 09:01, Jordi Blasco wrote: Good morning, In general, each MPI implementation require some additional configuration options in order to enable full support for a particular workload manager. In addition to that, some MPI versions also require additional environment

[easybuild] Workload managers support

2017-03-09 Thread Jordi Blasco
Good morning, In general, each MPI implementation require some additional configuration options in order to enable full support for a particular workload manager. In addition to that, some MPI versions also require additional environment variables or even different syntax/options in the