TWiki> EGEE Web>YAIM>YAIMcertification (revision 46)EditAttachPDF

YAIM Certification


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.

YAIM certification process

YAIM certification is done in three different stages:

  1. Initial testing: done by YAIM developers before starting the official certification process.
    • The patch is in the state 'in configuration'
    • YAIM rpms to be tested are then in /afs/ (alternatively but there will be no directory in the certification repository. The specific rpms under test must be listed in the patch, but this can change as problems are found.
  2. Certification - Fresh install testing: when YAIM developers consider the code is ready, certification starts.
    • the patch is in the state 'in certification'
    • The rpms are created in ETICS and are of 'release candidate' quality. They are then moved to /afs/ and the usual patch directory in the cert repository is created. Fresh installation is tested.
  3. Certification - Upgrade testing: when fresh installation testing is finished, upgrade testing can be done.
    • the patch is in the state 'in certification'
    • 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 stages.

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

Note YAIM is an exception to the general rule, whereby a patch in 'in configuration' will have an entry in the cert repo.

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

Edit | Attach | Watch | Print version | History: r50 | r48 < r47 < r46 < r45 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r46 - 2007-07-13 - OliverKeeble
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EGEE All webs login

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