Service Discovery Test Procedure

Set up a bdii on some machine

As root:
  • 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

As root:
  • 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-sd-cpp 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


     cd ~
     mkdir -p sdtest
     cp -r  /opt/glite/share/doc/glite-saga-adapters-* sdtest

     cd sdtest/glite-saga-adapters-cpp
     make
     make NUM=two
    ./sd_example_one
    ./sd_example_two

    cd ../glite-saga-adapters-java
    export CLASSPATH=$JAVA_SAGA_LOCATION/lib/*:.
    javac  SDExampleOne.java SDExampleTwo.java
    java -Dsaga.location=$JAVA_SAGA_LOCATION SDExampleOne
    java -Dsaga.location=$JAVA_SAGA_LOCATION SDExampleTwo

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


    cd ..
    cvs co org.glite.saga-adapter.sd-cpp/test
    cd org.glite.saga-adapter.sd-cpp/test
    ./tests.pl <bdii> <delay>

    cd ../..

    cvs co  org.glite.saga-adapter.sd-java/test
    cd org.glite.saga-adapter.sd-java/test
    ./tests.pl <bdii>

-- SteveFisher - 13-Nov-2009

Edit | Attach | Watch | Print version | History: r9 < r8 < r7 < r6 < r5 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r7 - 2010-03-08 - DrSMFisher
 
    • 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