NOTICE: FULL O2 Cluster Outage, January 3 - January 10th

O2 will be completely offline for a planned HMS IT data center relocation from Friday, Jan 3, 6:00 PM, through Friday, Jan 10

  • on Jan 3 (5:30-6:00 PM): O2 login access will be turned off.
  • on Jan 3 (6:00 PM): O2 systems will start being powered off.

This project will relocate existing services, consolidate servers, reduce power consumption, and decommission outdated hardware to improve efficiency, enhance resiliency, and lower costs.

Specifically:

  • The O2 Cluster will be completely offline, including O2 Portal.
  • All data on O2 will be inaccessible.
  • Any jobs still pending when the outage begins will need to be resubmitted after O2 is back online.
  • Websites on O2 will be completely offline, including all web content.

More details at: https://harvardmed.atlassian.net/l/cp/1BVpyGqm & https://it.hms.harvard.edu/news/upcoming-data-center-relocation

How to Generate SSH Keys

Owned by Kathleen Chappell
Last updated: Jan 11, 2022 by Andy Bergman
2 min read

Generating ssh keys enables you to streamline authentication on O2 without typing your password.

Host keys for all O2 compute nodes are already listed in /etc/ssh/ssh_known_hosts, so there is no need for you to add them to your ~/.ssh/known_hosts file.

First, create your public and private key combination

  • To create keys for connecting from one O2 system to another, run the following ssh-keygen command from an O2 login server.

  • To create keys for connecting from your desktop to O2, run the following ssh-keygen command (or equivalent) on your desktop.

$ ssh-keygen -t rsa Generating public/private rsa key pair. Enter file in which to save the key (/home/mfk8/.ssh/id_rsa): Enter passphrase (empty for no passphrase): Enter same passphrase again: Your identification has been saved in /home/mfk8/.ssh/id_rsa. Your public key has been saved in /home/mfk8/.ssh/id_rsa.pub. The key fingerprint is: a5:b5:38:73:b7:3c:a6:8a:1d:a8:bd:87:4e:be:33:21 mfk8@login01

For either desktop or intra-O2 usage, append the public key to the authorized_keys file in your O2 home directory:

$ cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys

Since the default new file permission will prevent these keys from being read by ssh, you will need to change it, and possibly also the parent .ssh directory.

$ chmod 0600 ~/.ssh/authorized_keys $ chmod 0700 ~/.ssh



Now, you should be able to ssh within O2 and the Transfer Cluster nodes without password. If after doing all the above steps, you're still asked for password when logging in then make sure your home directory has no group write permissions.





Note 1: Since your private key is not protected with a password, only use this key when working with O2 nodes. Do not use the public key for systems outside O2 without protecting it with a password. 

Note 2: This needs to be done only one time.

Note 3: If you have already done the above steps in Orchestra (our cluster that has been retired) you should not need to repeat this step in O2 since the /home filesystem is the same.  

Digital Accessibility