Shell

Preliminary information! Does not work as intended yet. Will reboot often!

Intention

• the computer pool is extended by these machines
• the computer pool infrastructue is accessible from remote

Target audience

These machines are meant to be used by students. But of course they can be used by any staff members! For new users the only requirement is to logon one single time using one of the (physical) pool computers - this will make them "known" to our systems.

Legacy login

Both login.stud.informatik.uni-goettingen.de and login.informatik.uni-goettingen.de are not affected by these new machines. They will continue to work unmodified.

Usage

Simply use SSH to login to this machine:

ssh  user@shell.stud.informatik.uni-goettingen.de

Note that the intially presented banner contains something like

#######  shell.stud.informatik.uni-goettingen.de - login vm: shell5.cip.loc

...telling you the actual local name of the automatically chosen destination machine.

For Windows: use PuTTY (simple) or Cygwin (more complex and powerful) or any other SSH-implementation.

Timeout

The session Timeout is set to 36 hours

Availability

Take a look at: http://shell.stud.informatik.uni-goettingen.de/ -- use ifi/ifi to login ("bots not welcome")

Some technical Details

• the gateway machine is running HAproxy. This is the only machine with a "real" IP-address.
• several shellX.cip.loc-machines are placed into the computer pool network. This is required to have exactly the same experience as if being physically in the pool
• all machines are virtual instances on one single host, the host has
  • 128 GiB ECC Ram
  • dual Xeon CPU
  • 600 GB Raid 1 local disk
  • 10 GBit/s networking :-)

Tips 'n' Tricks

Connect to the same machine again

Ignoring the Round-Robin mechanism is possible: connect to a specific port 42000+n withh n={1..6} :-)

For maschine number 4:

~$ ssh -p 42004 gtest2@shell.stud.informatik.uni-goettingen.de
#######
#######  shell.stud.informatik.uni-goettingen.de - login vm: shell4.cip.loc

Todo

• how to connect to a specific destination?
• Monitoring
• Documentation
• Testing

See also

• Remote Access
• Long Running Processes

Links

• https://help.ubuntu.com/ -- common help regarding Ubuntu
• http://shell.stud.informatik.uni-goettingen.de/ -- current state