[Ocfstest-commits] colinzhu commits r49 - trunk/Docs
svn-commits at oss.oracle.com
svn-commits at oss.oracle.com
Thu May 26 02:53:55 CDT 2005
Author: colinzhu
Date: 2005-05-26 02:53:52 -0500 (Thu, 26 May 2005)
New Revision: 49
Removed:
trunk/Docs/README
trunk/Docs/README.quickstart
Log:
These contents already merged
Deleted: trunk/Docs/README
===================================================================
--- trunk/Docs/README 2005-05-26 07:52:49 UTC (rev 48)
+++ trunk/Docs/README 2005-05-26 07:53:52 UTC (rev 49)
@@ -1,150 +0,0 @@
- Quick Start for automatic ocfs2 testing kits
-
-Steps to build and run current test cases:
-
-1, Fetch source from oss.oracle.com via svn:
-
-[root at node2 opt]# svn checkout http://oss.oracle.com/projects/ocfstest/src/trunk/ /opt/ocfs2test
-
-2, Enter ocfs2test bin directory and do configuration work (finish all the "make" needed and build some other files needed)
-
-[root at node2 opt]# cd /opt/ocfs2test/bin
-[root at node2 bin]# ls
-config_ocfs2.sh test_ocfs2.sh
-[root at node2 bin]# ./config_ocfs2.sh
-
-And it will build all the source need to be made. And brought the contents of the configuration file to your screen (which locates at </opt/ocfs2test>/ocfs2test/src/TestSuites/ocfs2test/tset/testenv.sh). Modify the settings in this file to be suitable for your environment if you need.
-
-3, Still in the bin directory, start the automatic testing:
-
-[root at node2 bin]# ./test_ocfs2.sh
-
-And wait for some time until all the cases are done.
-
-4, After all the cases done, report for all the cases will be displayed on screen. But you can still find it at </opt/ocfs2test>/ocfs2test/src/TestSuites/ocfs2test/tset/log if you missed screen output.
-
-Tips:
-Opening another terminal window and monitor system with "tail -f /var/log/messages" is a good way to learn what happens in system now. (Congratulations if you saw any "Call Trace" or Oops....... :D )
-
-Comments:
-1, All the testing cases are running in a way that it generated some results by operations in current environment (all the individual system specified info are tried to filtered, just common info left) and compare these results with standard result files. So if in future version standard output by ocfs2/tools are changed, related standard result files also need to be re-made.
-
-2, Current standard result files are based on ocfs2 svn 2097 and ocfs2tools svn 767
-
-3, Case B2 (mkfs.ocfs2) may fail for ocfs2tools svn versions later than svn 792 since after that mkfs.ocfs2 changed a lot. (Please make a new rpm for us to build a new standard result. :) )
-
-4, Case B4 should be more meaningful if we run some data corruption simulations before.
-
-5, In case B7, if we change the parameters of the width and level numbers of the deep directory tree to large numbers. This case may crash with "Segmentation Fault" errors.
-
-6, The standard result file for case B9 is an error message in fact, since mmap() functions are not implemented totally in current ocfs2 build yet.
-
-7, Case B11 is blank since no ioctl() call implemented. (Any updates recently?)
-
-8, The result for case B14 is different with the expected results in test plan.
-
-9, The result for case B17 is different with the expected results in test plan.
-
-10, The result for case B19 is different with the expected results in test plan.
-
-
-How to setup ocfs2test suites manually
-
-+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
-1. Check out source code of ocfstest according the instruction on oss.oracle.com.
-
-2. Please go to the directory of tet source, for example your_checkout_directory/ocfs2test/dependencies/tet.
-Then run "make" and "make install" to generate rpms for tet installation. Please pay attention to the output
-message of make command to create according directory and copy according files to get correct result.
-
-3. Please find the path information of newly generated tet rpm according to the output message of "make rpm",
-then install this rpm to complete tet installation.
-
-4. For tvs installation, please refer to tet installation steps.
-
-5. After successful installtion of tet and tvs, you should find the newly generated directory of /usr/tet and
-/usr/tet/TVS. Please add TVS_ROOT(/usr/tet/TVS), TVS_ROOT/bin and /usr/tet/bin into your PATH parameter.
-6. Please go to /usr/tet/TVS and create src directory. Then please move your_checkout_directory /ocfs2test/src/
-TestSuites to your newly created directory.
-
-7. Please run "make" and "make install" step by step under /usr/tet/TVS/src/TestSuites. After your running,
-new directory of /usr/tet/TVS/tsets/ocfs2test would be created.
-
-8. Here, please modify the setup.sh testenv.sh test.config file to reflect your configuration.
-
-9. Please go to /usr/tet/TVS/etc to edit the TVSListing file. First we need to delete the content in the original
-file including example test secnario and add new ocfs2 test secnario instead. For example, you can select to run
-tpstress test only by insert "ocfs2test tpstress" into TVSListing file. Here, we recommend we should run all the
-ocfs2 tests together to save time.
-
-10. Before running ocfs2 tests, please defind OCFSROOT system parameter to the directory your test root directory
-which have to locate under your ocfs2 partition. For example, you can specify this parameter in your .bash_profile
-with "export OCFSROOT=/ocfs2". Please take note you need to define this parameter on all your test
-nodes in your testing environment.
-
-11. Since we need use password-less ssh login in several tests, please ensure you already configured your environment
-before.
-
-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
-
-
-
Deleted: trunk/Docs/README.quickstart
===================================================================
--- trunk/Docs/README.quickstart 2005-05-26 07:52:49 UTC (rev 48)
+++ trunk/Docs/README.quickstart 2005-05-26 07:53:52 UTC (rev 49)
@@ -1,50 +0,0 @@
- Quick Start for automatic ocfs2 testing kits
-
-Steps to build and run current test cases:
-
-1, Fetch source from oss.oracle.com via svn:
-
-[root at node2 opt]# svn checkout http://oss.oracle.com/projects/ocfstest/src/trunk/ /opt/ocfs2test
-
-2, Enter ocfs2test bin directory and do configuration work (finish all the "make" needed and build some other files needed)
-
-[root at node2 opt]# cd /opt/ocfs2test/bin
-[root at node2 bin]# ls
-config_ocfs2.sh test_ocfs2.sh
-[root at node2 bin]# ./config_ocfs2.sh
-
-And it will build all the source need to be made. And brought the contents of the configuration file to your screen (which locates at </opt/ocfs2test>/ocfs2test/src/TestSuites/ocfs2test/tset/testenv.sh). Modify the settings in this file to be suitable for your environment if you need.
-
-3, Still in the bin directory, start the automatic testing:
-
-[root at node2 bin]# ./test_ocfs2.sh
-
-And wait for some time until all the cases are done.
-
-4, After all the cases done, report for all the cases will be displayed on screen. But you can still find it at </opt/ocfs2test>/ocfs2test/src/TestSuites/ocfs2test/tset/log if you missed screen output.
-
-Tips:
-Opening another terminal window and monitor system with "tail -f /var/log/messages" is a good way to learn what happens in system now. (Congratulations if you saw any "Call Trace" or Oops....... :D )
-
-Comments:
-1, All the testing cases are running in a way that it generated some results by operations in current environment (all the individual system specified info are tried to filtered, just common info left) and compare these results with standard result files. So if in future version standard output by ocfs2/tools are changed, related standard result files also need to be re-made.
-
-2, Current standard result files are based on ocfs2 svn 2097 and ocfs2tools svn 767
-
-3, Case B2 (mkfs.ocfs2) may fail for ocfs2tools svn versions later than svn 792 since after that mkfs.ocfs2 changed a lot. (Please make a new rpm for us to build a new standard result. :) )
-
-4, Case B4 should be more meaningful if we run some data corruption simulations before.
-
-5, In case B7, if we change the parameters of the width and level numbers of the deep directory tree to large numbers. This case may crash with "Segmentation Fault" errors.
-
-6, The standard result file for case B9 is an error message in fact, since mmap() functions are not implemented totally in current ocfs2 build yet.
-
-7, Case B11 is blank since no ioctl() call implemented. (Any updates recently?)
-
-8, The result for case B14 is different with the expected results in test plan.
-
-9, The result for case B17 is different with the expected results in test plan.
-
-10, The result for case B19 is different with the expected results in test plan.
-
-
More information about the Ocfstest-commits
mailing list