(r7) Cream_blah_testsuites < IGIRelease

Tags: , view all tags
---+!! Cream regression, BLAH functionality and regression testsuites installation, configuration and use 

%TOC%

---+ cream_blah_testsuite installation

---++ Prerequisite: cream_testing  (i.e. cream functionality testsuite) installed
All cream and blah testsuites (functionality and regression) work "over" a EMI User Interface. First step:
   * install a emi user interface
   * create your user
   * install your user certificate 
   * test your EMI UI with a simple job submission. 

EMI UI installation and configuration instructions are available [[https://wiki.italiangrid.it/twiki/bin/view/IGIRelease/IgiEmi#UI_Installation_and_Configuratio][here]].

When the UI is running, be sure that the environment variable X509_USER_PROXY is set to your proxy path (something like /tmp/x509up_u0). If not, set it.

cream_blah_testsuites depend from cream_test testsuite. Second step:
   * install cream_test testsuite.

cream_test testsuite installation, configuration and use instructions are available [[https://twiki.cern.ch/twiki/bin/view/EMI/CREAMRobotFuncTests][here]].

---++ Set italiangrid repository
Repository Not Available now.

---++ Install cream_blah_testsuite
Get the last cream_blah_testsuites rpm available[[https://github.com/italiangrid/cream_blah_testsuites/downloads][here]] and install it with:
<verbatim>
yum install cream_blah_testsuites-X.Y-Z.noarch.rpm 
</verbatim>

Note: EMI UI and cream_test must be already installed to be able to install cream_blah_testsuites.

---++ Set SSH keys authentication
Since cream_test 1.8 it is provided a script to semi-automate the process, check in cream_test installation and documentation.

Tha manual procedure is the standard procedure to grant ssh key access in linux:

   * From EMI UI where testsuites are installed create an ssh rsa key pair for host validation, here's how:
   <verbatim>
     my-ui:~# ssh-keygen -t rsa
   </verbatim>

   * Now you need to copy the public key to the CREAM CE to be tested (do NOT copy the private key), obviously use scp to do this
   <verbatim>
     my-ui:~# scp ~/.ssh/id_rsa.pub root@my-ce:~
   </verbatim>

   * Connect to the CREAM CE (my-ce):
   <verbatim>
     my-ui:~# ssh root@my-ce
   </verbatim>

   * Check out .ssh stuff, if .ssh dir doesn't exist you need to create it
   <verbatim>
     my-ce ~ # ls -la ~/.ssh
     ls: cannot access /root/.ssh: No such file or directory
     my-ce ~ # mkdir .ssh
     my-ce ~ # chmod 700 .ssh
   </verbatim>

   * Now copy your ssh public key into authorized keys file and delete it when finished:
   <verbatim>
     my-ce ~ # cat ~/id_rsa.pub >> .ssh/authorized_keys
     my-ce ~ # chmod 600 .ssh/authorized_keys
     my-ce ~ # rm id_rsa.pub
   </verbatim>

   * Test if the setup is correct. You must be able to copy or to connect to the CREAM CE from the EMI UI without supplying passwd:

Note:

Sometimes additional configurations are requested on remote ssh daemon, this may vary from basic security configuration. If final test failed you probably have PublicAuthentication or RSA disabled.
In this case you need to change them (it doesn't affect or lower your current security). Tipically this change is done by editing /etc/ssh/sshd_config file or better (for security) the user-specific ~/.ssh/config. 
To get the correct configuration, see that the following attributes are set (not commented or set to "no") in your sshd_config or ~/.ssh/config file
RSAAuthentication    yes
PubkeyAuthentication yes

If you change sshd_config file with these values you need to restart ssh daemon (/etc/init.d/sshd restart)

Note: Thanks to Andrea Benini Ben for [[https://www.linux.com/community/blogs/129-servers/13083][this page]] 
---++ Configure cream functionality testsuite
Edit and customize
<verbatim>
/opt/cream_test/lib/vars.py
</verbatim>

---++ Configure cream_blah_testsuites
   * Create the cream_blah testsuites configuration file:
   <verbatim>
     cp /opt/cream_blah_testsuites/lib/conf/cream_testsuite_conf.ini.template /opt/cream_blah_testsuites/lib/conf/cream_testsuite_conf.ini
   </verbatim>
   and customize it. Be careful:
      * Set the right middleware version installed in the ce under test
      * Set the right path of the yaim configuration files (site-info-path) and be sure they are editable
      * Check the blah_parser parameter value. It must be adequate to the blparser version (old or new) and batch system
   * In the user shell  you will use to launch tests source the file: /opt/cream_blah_testsuites/testsuite_env.sh 
   <verbatim>
     source /opt/cream_blah_testsuites/testsuite_env.sh 
   </verbatim>
   It will setup the environment needed to run the testsuites.
   * Set python4 pythonpath doing:
   <verbatim>
   export PYTHONPATH=/usr/lib/python2.4/site-packages:$PYTHONPATH
   </verbatim>

---+ Testsuite run
A generic description on how to run tests in cream testsuites is available [[https://twiki.cern.ch/twiki/bin/view/EMI/CREAMRobotFuncTests#Test_Execution][here]].

   * At first create a user proxy:
    <verbatim>
    voms-proxy-init -voms <VO>
    </verbatim>

   * Caveats:
      *  lauch the testsuites in a shell where you run previously /opt/cream_blah_testsuites/testsuite_env.sh and set PYTHONPATH
      * lauch the testsuites in a shell where you have write permissions: robot fremework tryes to write log files in the path where it is launched and it fails if it is unable to create its logs.

---++ Run BLAH testsuites


   * Run BLAH functionality testsuite:
<verbatim>
   pybot /opt/cream_blah_testsuites/testsuites/blah_testing/tests
</verbatim>
   * Run BLAH functionality tests one by one:
<verbatim>
   pybot /opt/cream_blah_testsuites/testsuites/blah_testing/tests/check_notifications_for_normally_finished_jobs.html
   pybot /opt/cream_blah_testsuites/testsuites/blah_testing/tests/check_notifications_for_cancelled_jobs.html
   pybot /opt/cream_blah_testsuites/testsuites/blah_testing/tests/check_notifications_for_suspended_resumed_jobs.html
</verbatim>
   * Run BLAH regression tests for cream configured with old blparser
<verbatim>
   pybot -i old_parser /opt/cream_blah_testsuites/testsuites/blah_regression/tests/bug_*.html
</verbatim>
   * Run all BLAH regression tests for cream configured with new blparser
<verbatim>
   pybot -i new_parser /opt/cream_blah_testsuites/testsuites/blah_regression/tests/bug_*.html
</verbatim>
   * Run BLAH regression tests for a specific release, ex. blah 1.18.0
<verbatim>
   pybot -i blah_1.18.0 /opt/cream_blah_testsuites/testsuites/blah_regression/tests/bug_*.html
</verbatim>
   * To switch *from old to new blparser* you have to: 
      * Go to the cream ce, set <verbatim>BLPARSER_WITH_UPDATER_NOTIFIER=true</verbatim> in <verbatim><site_info_dir>/services/glite-creamce</verbatim> and reconfigure using yaim.
      * In file /opt/cream_blah_testsuites/lib/conf/cream_testsuite_conf.ini set in section [blah_specific]:
        <verbatim>
        parser_type = with_updater_notifier
        parser_log_file = /var/log/cream/glite-ce-bnotifier.log
        </verbatim>
   * To switch *from new to old blparser* you have to: 
      * Go to the cream ce, set <verbatim>BLPARSER_WITH_UPDATER_NOTIFIER=false</verbatim> in <verbatim><site_info_dir>/services/glite-creamce</verbatim> and reconfigure using yaim.
      * In file /opt/cream_blah_testsuites/lib/conf/cream_testsuite_conf.ini set in section [blah_specific]:
        <verbatim>
        parser_type = with_blparser_only
        parser_log_file = /var/log/cream/glite-lsfparser.log
        </verbatim>

---++ Run CREAM regression testsuite
   * Run all CREAM regression tests
<verbatim>
   pybot  /opt/cream_blah_testsuites/testsuites/cream_regression/tests/bug_*.html
</verbatim>

---+ Versions compatibility
   * cream_blah_testsuite-0.1-0 is tested with cream_test-1.8.el5-1 and python 2.6

-- Main.SaraBertocco - 2012-10-12
Topic revision: r7 - 2012-11-12 - SaraBertocco
Account
- Log In
~~Edit~~
~~Attach~~