Howto access the cluster
You need a KU login to get access to this cluster. Ask imsupport to get access rights.
Accessing the cluster
First step: Bastion host
First login to our bastion host:
Substitute <KU-login> with your KU login name. Your password is the same as on KUnet etc. If you want to access ssh-diku-image from the cluster you may need to add SCIENCE\\ in front of your KU login.
Second step: Accessing the cluster servers
Now you can login to the cluster by doing the following.
Access to the storage servers:
ssh <KU-login>@nfs1-diku-image.science.ku.dk ssh <KU-login>@nfs2-diku-image.science.ku.dk
Acess to the compute servers:
ssh <KU-login>@compute01-diku-image.science.ku.dk ssh <KU-login>@compute02-diku-image.science.ku.dk ssh <KU-login>@compute03-diku-image.science.ku.dk ssh <KU-login>@compute04-diku-image.science.ku.dk
Substitute <KU-login> with your KU login name. Your password is the same as on KUnet etc.
Currently we have trouble with the Science-IT user authentication system so yoou login to the nfs and compute servers with your KU login with '-l' (small letter L) appended, e.g. <KU-login>-l.
We have made user accounts for all current members of the image group. Your password is the same as your diku password. However if you do not have an account you should contact an administrator. Currently the administrators are Stefan, Kim and Jon.
Notice that currently if you change your diku password you will not change your cluster password or vice versa.
Accessing the cluster
All access to the cluster is through one of the diku bastion hosts (ask, tyr, brok). From these hosts you use ssh to connect to the cluster. Ex. to connect to imagediskserver3 you do.
ssh -Y 192.168.10.103
Your user account home directory is located under /home.
NOTE: Currently the name handling on the diku system is not configured correctly so we can NOT use the cluster machine names from the bastion hosts (ask, tyr, brok), but have to use their IP addresses. On the cluster machines you CAN use the host names instead of the IP addresses.
For your convenience the IP addresses are given below:
# File servers 192.168.10.101 imagediskserver1 (out of order) 192.168.10.102 imagediskserver2 (out of order) 192.168.10.103 imagediskserver3 % IBM blade servers 192.168.10.111 imageserver1 192.168.10.112 imageserver2 (out of order) 192.168.10.113 imageserver3