[Ocfstest-commits] colinzhu commits r47 - trunk/Docs

[svn-commits at oss.oracle.com]

Author: colinzhu
Date: 2005-05-25 04:35:57 -0500 (Wed, 25 May 2005)
New Revision: 47

Modified:
   trunk/Docs/README
Log:
Instructions added



Modified: trunk/Docs/README
===================================================================
--- trunk/Docs/README	2005-05-25 09:32:46 UTC (rev 46)
+++ trunk/Docs/README	2005-05-25 09:35:57 UTC (rev 47)
@@ -88,3 +88,63 @@
 12. After you finish all the previous configuration, please simply run "tvs run" to run all the ocfs2 tests.
 
 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+
+Appendix A:  Configure the password-less ssh login between testing nodes
+
+	We can use ssh or rsh to run commands on remote nodes and return output to local node. In most cases (ssh/rsh) login must be password-less during testing for the convenience to build automatic testing process.
+
+	To set up secure, password-less login via SSH for user: (e.g  oracle user )
+
+	a. Generate the users's public and private SSH keys (~/.ssh/id_dsa.pub and id_dsa), as the oracle user:
+      	$ ssh-keygen -t dsa
+
+	i. "Enter file in which to save the key ...:" --> Press ENTER.
+	ii. "Enter passphrase ...:" 
+		For LESS Secure connection just Press ENTER.
+		For Secure connection enter a passphrase only you will know.
+	iii. "Enter same passphrase again:" Either ENTER or passphrase.
+
+	Note: In a multi-server environment, user would repeat step 'a.' above on each server in the cluster before proceeding to step 'b.'
+
+	b. Create the authorized_keys file by combining the contents of the id_dsa.pub files from each server.  You can do this all on one node by running the command below multiple times, replacing "raclinux1" with a different node name each time.  As the oracle user:
+
+	$ ssh raclinux1 "cat ~/.ssh/id_dsa.pub" >> ~/.ssh/authorized_keys
+
+	i. Each time you connect from any node to a new hostname for the first time, you will see a message similar to:
+
+            "The authenticity of host 'raclinux1 (192.168.203.11)' can't be
+            established.  RSA key fingerprint is ...
+            Are you sure you want to continue connecting (yes/no)?"
+
+         Type "yes" and press ENTER.  You will then see the message:
+
+            "Warning: Permanently added 'raclinux1,***.***.***.***' (RSA) to
+            the list of known hosts."
+
+	ii. "oracle at raclinux1's password:"  --> Type "oracle" and press ENTER.
+
+         Note: In a multi-server environment, copy the authorized_keys file
+         you just created to the ~/.ssh directory of the oracle user on each
+         server in the cluster.  For example, you could use the following
+         command to copy it to node "raclinux2":
+   
+         $ scp ~/.ssh/authorized_keys raclinux2:/home/oracle/.ssh/
+	 oracle at raclinux2's password:  --> Type "oracle" and press ENTER.
+
+	c. (Optional) If you entered passphrase above, and desire password-less login, you need to inform the ssh-agent (already running for desktop) of the passphrase so that ssh clients would not be prompted for a passphrase.  Once you notify ssh-agent the passphrase is cached for duration of the GUI desktop login, and further client requests are satisfied by the ssh-agent.
+       
+         $ ssh-add
+         Enter passphrase for /home/oracle/.ssh/id_dsa: *TYPE YOUR PASSPHRASE*
+         Identity added: /home/oracle/.ssh/id_dsa (/home/oracle/.ssh/id_dsa)
+
+	d. (not optional) To finalize and test the password-less SSH connection, answer YES to any prompt:
+
+	i. Run "ssh raclinux1 date".
+	ii. Run "ssh raclocal1 date".
+	iii. Run "ssh raclinux1.us.oracle.com date".
+	iv. Run "ssh raclocal1.us.oracle.com date".
+
+   Note: In a multi-server environment, repeat above steps to all nodes
+
+
+