These are chat archives for ipython/ipython
In http://ipyparallel.readthedocs.org/en/latest/process.html?highlight=template#using-ipcluster-in-pbs-mode you write:
Once you have created these scripts, save them with names like pbs.engine.template. Now you can load them into the ipcluster_config with [...]
Is there a reason for this dot style file name and where do you actually store these files?
Just because I configured the controller to be on the login node does not mean that my LSF engines are launched from the controller host, does it?
Is there a config that tells ipython: "Whenever I want to start new engines via bsub, please ssh into the login node first and run bsub commands there"?
ssh <HOST> ipcluster engines -n <N>"
SSHProxyEngineSetLauncher, right? Are there docs what to write in the config files for that?
c.IPClusterEngines.engine_launcher_class = 'SSHProxyEngineSetLauncher'
[login node]$ ipython profile create --parallel
[login node]configure default profile to use LSF (
c.IPClusterEngines.engine_launcher_class = 'lsf')
[laptop/etc.]$ ipython profile create --parallel
[laptop/etc.]configure profile to use SSHProxy, set
SSHProxyEngineSetLauncher.hostname = 'cluster_host'
SSHProxyEngineSetLauncherconnects successfully via ssh to the login node, the login node then starts the
LSFEngineSetLauncher. Unfortunately, at this point things go awry. Despite of being on the node, I see
[D 16:56:56.983 NotebookApp] b'/bin/sh: bsub: command not found\r'in the debug log. Is there any chance that I can give the full path to bsub to see if there's a sourcing issue?
submit_command, but setting
c.PBSEngineSetLauncher.submit_command = blaon the login node has no effect as far as I can see.