| Both sides previous revision
Previous revision
Next revision
|
Previous revision
Next revision
Both sides next revision
|
cluster:93 [2011/01/11 15:47]
hmeij |
cluster:93 [2011/01/11 16:36]
hmeij |
| * If you modify a file on greentail's new home dirs that //also// exists on the old homes dirs, you will loose your changes when the weekly refresh happens. | * If you modify a file on greentail's new home dirs that //also// exists on the old homes dirs, you will loose your changes when the weekly refresh happens. |
| |
| To avoid a conflict between home dirs I strongly suggest you create a directory to store the files you will be creating on greentail, for example /home/username/greentail or /home/username/hp. | To avoid a conflict between home dirs I strongly suggest you create a directory to store the files you will be creating on greentail's new home dirs, for example /home/username/greentail or /home/username/hp. That way the weekly refresh will not interfere with new files created on greentail. |
| |
| At some point in the future, greentail's new home dirs will be mounted on the petaltail/swallowtail and sharptail clusters. Filer3's old home dirs will then disappear permanently. | At some point in the future, greentail's new home dirs will be mounted on the petaltail/swallowtail and sharptail clusters. Filer3's old home dirs content will then disappear permanently. |
| |
| Greentail's new home dirs will provide 10 TB of disk space. Again, the clusters file system should not be used to archive data. However, doubling the home directory size should provide much needed relief. | Greentail's new home dirs will provide 10 TB of disk space. Again, the clusters file systems should not be used to archive data. Doubling the home directory size should provide much needed relief. |
| |
| Because of the size of the new home dirs, we will also not be able to provide backup via TSM (Tivoli). Backup via TSM to our Virtual Tape Library (VTL) will be replaced with disk to disk backup on greentail's disk array. That has some serious implications. Please read the section about RSnapshot. | Because of the size of the new home dirs, we will also not be able to provide backup via TSM (Tivoli). Backup via TSM to our Virtual Tape Library (VTL) will be replaced with disk to disk (D2D) backup on greentail's disk array. That has some serious implications. Please read the section about Rsnapshot. |
| |
| |
| ===== SSH Keys ===== | ===== SSH Keys ===== |
| |
| Within the directory **/home/username/.ssh** there is a file named **known_hosts**. Within this file are host level public SSH keys. Because your home directory contents are copied over to host greentail, you should be able to ssh from host petaltail or swallowtail to host greentail without a password prompt. If not, your keys are not set up properly. | You can log in to host greentail directly (''ssh username@greentail.wesleyan.edu''). VPN required for off campus access. |
| |
| You can also log in to host greentail directly (''ssh username@greentail.wesleyan.edu''). From host greentail should be able to to ssh to host petaltail or swallowtail without a password prompt. If not, your keys are not set up properly. | Within the directory **/home/username/.ssh** there is a file named **authorized_keys**. Within this file are public SSH keys. Because your home directory contents are copied over to host greentail, you should be able to ssh from host petaltail or swallowtail to host greentail without a password prompt. If not, your keys are not set up properly. You may need to add your ''id_rsa.pub'' content to this file. |
| |
| | Note: the software stack on host petaltail (administrative server) creates ssh keys for you automatically upon your first login, so for most of you this is all set. To set up your private/public ssh keys manually: |
| Note: the software stack on host petaltail/swallowtail created ssh keys for you automatically upon your first login, so for most of you this is all set. To set up your private/public ssh keys: | |
| |
| * log into a host, then issue the command ''ssh-keygen -t rsa'' | * log into a host, then issue the command ''ssh-keygen -t rsa'' |
| * then copy the contents of /home/username/.ssh/id_rsa.pub into the file authorized_keys | * then copy the contents of /home/username/.ssh/id_rsa.pub into the file authorized_keys |
| * you can have multiple public ssh key entries in this file | * you can have multiple public ssh key entries in this file |
| | |
| | The file **known_hosts** contains server level ssh keys. This is necessary for MPI programs to log into compute nodes withouot a password prompt and submit your jobs. That file has been prepped for you. |
| | |
| |
| |
