Service Discovery Test Procedure

Set up a bdii on some machine

• Download repos for glite_BDII and enable the dag repo

• yum install glite-BDII

• Download repo for lcg-CA and turn off gpgcheck (proxy problems)

• yum install lcg-CA

• add firewall rule to /etc/sysconfig/iptables

    -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 2170 -j ACCEPT

Set up test machine

• Reinstall with latest version SL5.x and yum update etc

• Download repos for glite_UI and enable the dag repo

• yum groupinstall glite-UI

• Download repo for lcg-CA and turn off gpgcheck (proxy problems)

• yum install lcg-CA

• If you need to clean out from an earlier set of RPMs: rpm -qa | grep -i saga | xargs yum -y remove

• yum install glite-saga-adapter-isn-java glite-saga-adapter-sd-java

• If the /opt/glite/yaim/node-info.d/glite-ui does not include config_glite_saga then modify /opt/glite/yaim/node-info.d/glite-ui to include config_glite_saga at the end of UI_FUNCTIONS

• copy site-info.def to opt/glite/yaim

• edit site-info.def enable just the ATLAS VO as in the example in the file and set BDII_HOST=lcg-bdii.gridpp.ac.uk and run: /opt/glite/yaim/bin/yaim -c -s site-info.def -n UI

• Install boost-devel to run the examples

As a normal user:

• Check for doc in /opt/glite/share/doc/glite-saga-adapters-* and ensure that it is clear and accurate

• man saga-sd and check the output

• man saga-isn and check the output

     mkdir -p ~/saga-adapter-tests
     cp -r /opt/glite/share/doc/glite-saga-adapters-cpp  ~/saga-adapter-tests/cpp
     cp -r /opt/glite/share/doc/glite-saga-adapters-java  ~/saga-adapter-tests/java
     
     cd ~/saga-adapter-tests/cpp/sd
     make
     make NUM=two
    ./sd_example_one
    ./sd_example_two

     cd ~/saga-adapter-tests/cpp/isn
     make
     make NUM=two
    ./isn_example_one
    ./isn_example_two

     cd ~/saga-adapter-tests/java/sd
     javac -cp $JAVA_SAGA_LOCATION/lib/'*' SDExampleOne.java SDExampleTwo.java
     java -cp  $JAVA_SAGA_LOCATION/etc/saga/java:$JAVA_SAGA_LOCATION/lib/'*':. -Dsaga.location=$JAVA_SAGA_LOCATION SDExampleOne
     java -cp  $JAVA_SAGA_LOCATION/etc/saga/java:$JAVA_SAGA_LOCATION/lib/'*':. -Dsaga.location=$JAVA_SAGA_LOCATION SDExampleTwo | head -8

    cd ~/saga-adapter-tests/java/isn
    javac -cp $JAVA_SAGA_LOCATION/lib/'*' ISNExampleOne.java ISNExampleTwo.java
    java -cp  $JAVA_SAGA_LOCATION/etc/saga/java:$JAVA_SAGA_LOCATION/lib/'*':. -Dsaga.location=$JAVA_SAGA_LOCATION ISNExampleOne
    java -cp  $JAVA_SAGA_LOCATION/etc/saga/java:$JAVA_SAGA_LOCATION/lib/'*':. -Dsaga.location=$JAVA_SAGA_LOCATION ISNExampleTwo | grep Location:

Run the C++ and Java tests. For the C++ test the should be specified as a machine where you have installed the test BDII as this will be modified to set fixed configuration files and is a time in seconds that should be long enough for the BDII server to repopulate itself after a restart - this depends upon the speed of the machine running the test BDII. Try 120 and increase it if you have problems. For the Java test any functioning top level bdii can be used. The tests should run to completion. Some tests include providing bad input to obtain error messages. These messages should be checked to ensure that they can be understood.

• Get a voms proxy

    export CVS_RSH=ssh
    export CVSROOT=:ext:fisher@glite.cvs.cern.ch:/cvs/glite

    cd ~/saga-adapter-tests
    cvs co org.glite.saga-adapter.sd-cpp/test
    cvs co  org.glite.saga-adapter.sd-java/test
    cvs co org.glite.saga-adapter.isn-cpp/test
    cvs co  org.glite.saga-adapter.isn-java/test

    cd ~/saga-adapter-tests/org.glite.saga-adapter.sd-cpp/test
   ./tests.pl rgma10 200 > sd-cpp.txt 2>&1

    cd ~/saga-adapter-tests/org.glite.saga-adapter.sd-java/test
    ./tests.pl lcg-bdii.gridpp.ac.uk > sd-java.txt 2>&1

    cd ~/saga-adapter-tests/org.glite.saga-adapter.isn-cpp/test
    ./tests.pl rgma10 200 > isn-cpp.txt 2>&1

    cd ~/saga-adapter-tests/org.glite.saga-adapter.isn-java/test
    ./tests.pl lcg-bdii.gridpp.ac.uk > isn-java.txt 2>&1

   * Check the four output files

   * Finally check that the configuration files work as indicated at the end of the SD user guides.

-- SteveFisher - 13-Nov-2009