Package: remote-ikernel-mosh
All your Jupyter kernels, on all your machines, in one place.Launch Jupyter kernels on remote systems and through batch queues so that
they can be used within a local Jupyter noteboook.Jupyter compatible Kernels start through interactive jobs in batch queue
systems (SGE, SLURM, PBS…) or through SSH connections. Once the kernel is
started, SSH tunnels are created for the communication ports are so the
notebook can talk to the kernel as if it was local.Commands for managing the kernels are included. It is also possible to useremote_ikernelto manage kernels from different virtual environments or
different python implementations.Install withpip install remote_ikernel. Requiresnotebook(as part
of Jupyter), version 4.0 or greater andpexpect. Passwordlesssshto the all the remote machines is also required (e.g. nodes on a cluster).NoteWhen running kernels on remote machines, the notebooks themselves will
be saved onto the local filesystem, but the kernel will only have access
to filesystem of the remote machine running the kernel. If you need shared
directories, set upsshfsbetween your machines.NoteVersion 0.3 and later of this package depend on the split Jupyter and
IPython versions when installing with pip. If you are upgrading
from an older version of IPython, Jupyter will probably migrate your
existing kernels (to~/.local/share/jupyter/kernels/), but not
profiles. If you need to stick with IPython 3 series, use an older
version ofremote_ikernelor install without using pip/setuptools.# Install the module ('python setup.py install' also works)pipinstallremote_ikernel# Set up the kernels you'd like to useremote_ikernelmanage# Add a new kernel running through GrideEngineremote_ikernelmanage--add\--kernel_cmd="ipython kernel -f {connection_file}"\--name="Python 2.7"--cpus=2--pe=smp--interface=sge# Add an SSH connection to a remote machine running IJuliaremote_ikernelmanage--add\--kernel_cmd="/home/me/julia-79599ada44/bin/julia -i -F /home/me/.julia/v0.3/IJulia/src/kernel.jl {connection_file}"\--name="IJulia 0.3.8"--interface=ssh\--host=me@remote.machine--workdir='/home/me/Workdir'--language=julia# Set up kernels for your local virtual environments that can be run
# from a single notebook server.remote_ikernelmanage--add\--kernel_cmd="/home/me/Virtualenvs/dev/bin/ipython kernel -f {connection_file}"\--name="Python 2 (venv:dev)"--interface=local# NEW!!
# Connect to a SLURM cluster through a gateway machine (to get into a
# local network) and cluster frontend machine (where the sqsub runs from).remote_ikernelmanage--add\--kernel_cmd="ipython kernel -f {connection_file}"\--name="Python 2.7"--cpus=4--interface=slurm\--tunnel-hostsgateway.machinecluster.frontendThe kernel spec files will be installed so that the new kernel appears in
the drop-down list in the notebook.remote_ikernel managealso has options
to show and delete existing kernels.WarningIJuliakernels don’t seem to close properly, so you may have julia
processes lingering on your systems. To work around this edit the file~/.julia/v0.3/IJulia/src/handlers.jlso thatshutdown_requestcallsrun(`kill$(getpid())`)instaed ofexit().Changes for v0.4Option--tunnel-hosts. When given, the software will try to create
an ssh tunnel through all the hosts before starting the final connection.
Allows using batch queues on remote systems.Preliminary support for dealing with passwords. If a program is defined
in the environment variableSSH_ASKPASSit will be used
to ask the user for a password.Changes for v0.3Updated pip requirements to pull in thenotebookpackage. Use an earlier
version if you need to use IPython 3.Remote process is polled for output which will show up when--verboseif used as a kernel option.Changes for v0.2Version 0.2.11 is the last version to support IPython notebook version 3.piprequirements enforce versions less than 4. Use a more recent version
to ensure compatibility with the Jupyter split.Support for PBS/Torque throughqsub-I.Tunnels are kept alive better, if something is not responding try waiting
20 seconds to see if a tunnel had dies. (Tunnels no longer depend on pyzmq,
instead they are launched through pexpect and monitored until they die.)--remote-launch-argscan be used to setqloginparameters or similar.--remote-precmdallows execution of an extra command on the remote host
before launching a kernel.Better compatibility with Python 3.Kernel output on terminals with--verboseoption for debugging.Connect to a host with ssh, slurm, or local kernels.Changed prefix torik_.kernel_cmd now requires the{connection_file}argument.remote_ikernel manage--showcommand to show existing kernels.Specify the working directory on the remote machine with--workdir.kernel-uuid.jsonis copied to the working director for systems where
there is no access to the frontend filesystem.Added compatibility layer to get rid of Jupyter warnings.