YAIM Certification

Introduction

This page contains information about the testing and certification activities done before a new release of YAIM is given to PPS. See the Yaim planning page for more information related to YAIM releases.

How to certify YAIM

YAIM certification is done in three different stages:

  1. Developers testing: done by YAIM developers before starting the official certification process. YAIM rpms to be tested are then in /afs/cern.ch/project/gd/www/yaim/testing/ , or the same location through http http://grid-deployment.web.cern.ch/grid-deployment/yaim/testing . During this stage, the patch is in the state 'in configuration', but there will be no specific rpms mentioned, and there will be no directory in the certification repository. Note this makes YAIM an exception to the general rule.
  2. Fresh install testing: when YAIM developers consider the code is ready, certification starts. YAIM rpms are then moved to /afs/cern.ch/project/gd/www/yaim/ and fresh installation is tested. New versions of the rpms can appear at this stage. The patch should now contain specific versions of rpms, which are of 'release candidate' quality, ie built remotely with ETICS. During this stage, the patch is in the state 'in certification'
  3. Upgrade testing: when fresh installation testing is finished and the rpms are mature enough, a Savannah patch is created. If the yaim module affects both 3.0 and 3.1 repositories, one patch per repository has to be created. The rpms are then created in ETICS and are made available for installation using the APT or YUM certification repositories. The certification testbed is then upgraded using the repositories and the upgrade is tested. SAM tests are run to test basic functionality. New versions of the rpms can also appear at this stage but this is less expected to happen than in the previous stage.

For stages 2 and 3, please follow the instructions described in the Certification checklist.

What to test in YAIM

  • Testing YAIM's functionalities
    • functions: local, pre and post functions are working correctly, it is visiblle, notif printed during configuration ?
    • correct sourcing of services, node-info.d, vo.d ? variables are correctly overwriting each other ?
    • does the presence of a new module really overwrite the behaviour of yaim-core ? E.g. a gliteCE is now configurable with glite-yaim-core (old python config) and also with glite-yaim-ce (new configuration) . Both should work , with the same syntax !
    • stale files after reconfig, stupid error messages, garbage, typos ?
    • how the environment settings influence the behaviour , YAIM should not take anything from the environment everything should be defined in site-info.def
    • Check the functioning of grid-env.csh (it's a big hack, but supposed to work).
    • Check the -check functionality. Not fully implemented, but should not cause error !
    • all the yaim modules should depend on yaim-core !
    • check where the temporary files are created and how (security issue!)
  • Testing upgrades
    • is it possible to install glite-yaim-core with the old and the new corrected metapackage ? The glite-yaim-core should obsolate and provide glite-yaim
    • testing conflicts
  • Testing fresh installs
    • Is fresh installation works 'out-of-the-box' ?
  • Testing SLC4 upgrade /fresh install of UI and WN.
    • Testing SLC4 install UI/WN
    • The same yaim is configuring now SLC4 and SLC3 WN with the same syntax , is it true ? Is the GLOBUS_TCP_PORT_RANGE variable correctly set ? With/without comma ?
  • Testing different node type combinations
    • Favorite combinations should be tested like:
      • CE_torque + BDII_site + SE_classic + MON
      • CE_torque + BDII_site + SE_classic + MON + UI
      • CE_torque + BDII_site + MON
      • lcg-RB + LFC_mysql + MyProxy + BDII(top level)
      • and similars.... (the ones above used in PPS/Prod)

YAIM Certification reports

-- AndreasUnterkircher - 11 Jun 2007


This topic: EGEE > YAIM > YAIMcertification
Topic revision: r45 - 2007-07-13 - OliverKeeble
 
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright & by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Ask a support question or Send feedback