Certification Procedures - gLite Certification - LCG Grid Deployment

SFT Test Suite in certification

Overview

SFT (Site Functional Tests) is a test application used to run basic functionality tests of a site. After the installation of a certification site is completed (e.g. with a new gLite release), we use to run SFT to be sure that, before running the heavier Certification Test Suite, at least the basic "communication tests" can be passed.

Installation and configuration

The "official" installation and configuration reference for the Site Functional Tests suite is

... on a deleted link. Please contact operational-documentation@mailmanNOSPAMPLEASE.egi.eu for the details.

That guide, maintained by Piotr Nyczyk is addressed to site administrators in the LCG production system.

If amendments have been made to run SFT in the gLite certification environment they are supposed to be listed here

Configure your CEs manually (certification)

Neither the certification site(s) nor their resources appear in the GOG db.

Therefore the list of CEs where to run the SFT tests have to be statically configured. This is a difference with the PPS environment.

Query the GOC db to obtain the list of CEs (pre-production)

This is not used in certification but in pre-production.

Basically the flow of information from the GOC db to the SFT works as follows:

  1. Sites and nodes are inserted by the site administrators into the GOC db.
  2. A script is used to query this information and populate appropriate tables on the R-GMA db.
  3. SFT queries the R-GMA and creates its own list of nodes.

If the tables GocSite_v0_4 and GocNode_v0_4 do not exist on the R-GMA server, you need to create them.

To create the GocSite_v0_4 and GocNode_v0_4 tables

You need the RGMA client installed so that the following commands can be run on a UI or on whatever machine had a RGMA client installed. You could install the client on the RGMA server itself (e.g the machine you are using as SFT server) BUT, in order to run the create_table utility (see later in the procedure) against a secure RGMA server (as the gLite one is) you need also a proxy, so it is definitely better to run on a UI.

  • log into a UI
  • download and install the create_table utility
    • > mkdir gocdb-xfer
    • > cd gocdb-xfer
    • > wget http://hepunx.rl.ac.uk/egee/jra1-uk/glite-r1/schema/create_table.tar.gz
    • > gunzip create_table.tar.gz
    • > tar xvf create_table.tar
  • create the tables
    • > voms-proxy-init -voms dteam (or equivalent)
    • > ./create_table "CREATE TABLE GocSite_v0_4 (siteID int primary key, officialname varchar(100), sitename varchar(100), friendlyname varchar(100), domain varchar(50), homeURI varchar(255), country varchar(50),  tier int, giisUrl varchar(250), inMonitoring varchar(1), status varchar(30), type varchar(30), region varchar(50), inMaintenance varchar(1))"
    • > ./create_table "CREATE TABLE GocNode_v0_4 (nodeID int primary key, siteID int, nodetype varchar(50), nodetype2 varchar(50), hostname varchar(50), domain varchar(200), ip varchar(15), grp varchar(20), hostdn varchar(255), monitor varchar(1))"

To populate the R-GMA with the data in the GOC db

  • Edit the file gocdb-xfer.conf and insert username and password of the GOC db. Ask Antonio Retico or Min Tsai if you don't know them.
####################################
# Config file for gocdb-xfer
####################################
# Default values: do not modify this section
[DEFAULT]

[gocdb]
dbhost = goc.grid-support.ac.uk
dbuser = <username>
dbpass = <password>
dbname = goc-2_0

  • Edit the file GocDB.py and insert the correct values for root_dir and config_path , e.g.

...
root_dir = "/home/aretico/gocdb-xfer/"
config_path = os.path.join(root_dir, "gocdb-xfer.conf")
...

  • Run the script to export data from the GOC db (it takes some minutes)
    • > chmod 700 gocdb-xfer.py
    • => ./gocdb-xfer.py

After the script finishes the sites should be visible in the RGMA browser but you have to run a "Continuous & old" query. That means that you are querying directly the producer and the data are only temporarily available. In order to instantiate a secondary producer and have the data permanently stored in the mysql database, you need a secondary producer and the archiver so you need the flexible archiver to be configured.

To configure the archiver on the RGMA server

  • Create a configuration file for the archiver. If there is alreandy an active one, create a copy
    • > cp ${GLITE_LOCATION}/etc/rgma-flexible-archiver/glue-config.props ${GLITE_LOCATION}/etc/rgma-flexible-archiver/glue-goc-config.props
    • edit ${GLITE_LOCATION}/etc/rgma-flexible-archiver/glue-goc-config.props adding the following two tables
... Glue tables ...

Table=GocNode_v0_4
RetentionPeriod=1440
CleanupInterval=1

Table=GocSite_v0_4
RetentionPeriod=1440
CleanupInterval=1

  • Configure the archiver with the new configuration file
    • In the R-GMA Server XML configuration file change the (advanced) parameter rgma.server.archiver_configuration_file as follows:
 
<rgma.server.archiver_configuration_file
   description="Configuration file to be used to setup the flexible-archiver database to
           to select which tables are supposed to be backuped. By default, the glue and 
           service tables are selected. (See also parameter 'rgma.server.run_archiver')
           [Example: '/my/path/my_config_file.props'] [Type: 'string']"
   value="${GLITE_LOCATION}/etc/rgma-flexible-archiver/glue-goc-config.props"/>
    • > /opt/glite/etc/config/scripts/glite-rgma-server-config.py --stop
    • > /opt/glite/etc/config/scripts/glite-rgma-server-config.py --configure
    • => /opt/glite/etc/config/scripts/glite-rgma-server-config.py --start

Use

The SFT client is deployed on a UI.

The results of the tests are published on our own SFT server installed on lxb1794.

-- Main.aretico - 14 Sep 2005

Edit | Attach | Watch | Print version | History: r8 < r7 < r6 < r5 < r4 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r8 - 2011-06-21 - AndresAeschlimann
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LCG All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback