Changes between Version 21 and Version 22 of HowTo/LoginToNodes

Timestamp:

08/02/12 17:26:50 (12 years ago)

Author:

nriga@bbn.com

Comment:

--

HowTo/LoginToNodes

@@ -51 +51 @@
 If you made your reservation with Omni then you will need to access the host where your Omni is installed to get a copy of your SSH Key. If you use the host that has Omni installed to ssh to your nodes then you skip to [ these instructions]. If you just want to get a copy of your private key and use it for logging into your nodes from another host, then you should :
   1. Login to the host where you have Omni installed
-  2. Open your omni configuration file. For most users this file is located at ~/.gcf/omni_config
-  3. 
+  2. Open your omni configuration file. For most users this file is located at ~/.gcf/omni_config. Also when you reserve resources using createsliver, omni prints the used configuration file towards the top. 
+  3. In the omni_config file there should be a section about your user that has an attribute called `keys', that has a list of all the public keys that are installed in the nodes. Usually in the same directory as the public keys there are also the private keys (a private key usually has the same name as the public key but without the '.pub' extension.
+  4. Copy the private key over to your host, either by using [http://en.wikipedia.org/wiki/Secure_copy scp] or any other file transfer protocol. You can also just copy-paste the contents of the file. 
 
 ==== Other tools ====
+Any tool that uses the GENI AM API to reserve resources, provides the public keys to the AM to be installed on the compute resources. If you can't figure out which keys the tool you used installed on the hosts, please send an email to [mailto:help@geni.net] telling us which tool you used and we will be happy to help. 
 
 == Managing SSH keys on Linux, Mac hosts ==