EGEE-II INFSO-RI-031688
Enabling Grids for E-sciencE
www.eu-egee.org
EGEE and gLite are registered trademarks
SA3 IFIC – report 27/11/2006
Álvaro Fernández
IFIC (CSIC)
2
Enabling Grids for E-sciencE
EGEE-II INFSO-RI-031688
IFIC in SA3
• 12 PM– Gabriel Amoros (6PM)– Alvaro Fernandez (6PM)– Javier Sanchez
• Officially – Task 3.2.3
• Tasks – Testing: WMS C++ API– Test Configuration and Exploitation of Job Priorities
3
Enabling Grids for E-sciencE
EGEE-II INFSO-RI-031688
Job Priorities
• Test Configuration and Exploitation of Job Priorities• Objetives
– Test policy enforcement based on VOMS groups– Configure testbed and check schema proposed by Job Priorities
WG (TCG)
• Work done– Configure testbed based on Torque/Maui with local policies on
resource sharing: 8 WN + 1 GliteCE + 1 LcgCE + 1 WMS + 1 MonBox + 1 UI Define local mappings for groups/roles and Fair shares (i.e: Atlas
80% of total share, rest 20% share) Queues: one per vo so far, to move 1 all. Defined “atlprod” queue
to check proper WMS matchmaking with role:/atlas/Role=production VOViews: one per group/role defined WMS: debug VOMS FQAN matchmaking
4
Enabling Grids for E-sciencE
EGEE-II INFSO-RI-031688
Job Priorities
• Problems/Issues– Missing parts at client side:
Attribute VOMS_FQAN not added by glite-job-list-match command (bug #18131, Ready for Review)
– WMS not matching correctly VOMS roles: VOMS fqan plugin not loading correctly (bug #18045, Fixed)
• Plans– Possibly test configuration based on yaim– Test more complex scenarios: not only local policies
5
Enabling Grids for E-sciencE
EGEE-II INFSO-RI-031688
WMS C++ API
• Objectives– Provide a test-suite to test the WMS C++API (client side)
check correctness check completeness
• Main tests– Unit testing – Some parts imply service tests
• Work done– Work on defining Test plan (
https://edms.cern.ch/document/674827/1 )– Test Plan:
Test JOB DESCRIPTION• Classes to manipulate JDLs, represent jobs (UNIT TESTS)
6
Enabling Grids for E-sciencE
EGEE-II INFSO-RI-031688
work done
JOB CONTROL• Classes to list resources, send jobs, cancel jobs.
• Requires TestBed ( UI, WMS, CE, WN) to check correctness
• Requires X509 Proxy SPECIFIC JOBS AND JOB COLLECTIONS
• Test specific classes dealing with interactive, dags, and collections of jobs
OTHER CLASSES• i.eBrokerInfo management
• Current implementation is about 50-60 % on the test plan.
• Available on cvs module org.glite.testsuites.wms-api• Built packages for glite3.0
7
Enabling Grids for E-sciencE
EGEE-II INFSO-RI-031688
work done
• Found problems and reported as bugs:– WMS C++ API - glite::wmsui::api::Job::listMatchingCE
method fails (bug #20863, None)– Attribute VOMS_FQAN not added by glite
-job-list-match command (bug #18131, Ready for Review)– C API crashes with a segmentation Fault (bug #17391, Ready f
or Review)– WMS C++ API: JobAd:check() deletes "type" attribute (dag
jobs) (bug #14459, Ready for Test)– Job::listMatchingCE gives incorrect anwser (WMS C++
API) (bug #12458, Ready for Test)– strange behaviour of Job::listMatchingCE ( using voms ) (bug
#12456, Ready for Test)– WMS C++ API crashes when using getStatus() method (bug
#10803, Accepted)
• Contacted and solved by JRA1
8
Enabling Grids for E-sciencE
EGEE-II INFSO-RI-031688
PROBLEMS / ISSUES
– Use CPPUNIT to carry out testing– TestManager to automate test calling, and generate HTML test
reports
• Problems / Issues– Change of API in glite3.1– Missing documentation for changes in 3.1– API not directly used by CLI– Some parts of the API not implemented– Cppunit not available as a package (solved now by ETICS)– Build server takes rather old TAG to build RPMS for glite3.0– Org.glite.testsuites not added to glite3.1 builts.
9
Enabling Grids for E-sciencE
EGEE-II INFSO-RI-031688
NEXT PLANS
• PLANS FOR NEXT MONTHS:– Use ETICS to build out RPMS– Include the test-suite in a common testing framework
Andreas suggested SAMe• already exists, and a good entry point.
• seems not difficult to adapt our tests to use it
• seems more service test oriented. Maybe have a look at ETICS framework: possible to include the
unit tests (???)
– Complete implementation based on defined test plan