80 likes | 187 Views
SA3 IFIC – report 22/05/2007. Álvaro Fernández IFIC (CSIC). IFIC in SA3. 12 PM Gabriel Amoros (6PM) Alvaro Fernandez (6PM) Javier Sanchez Officially Task 3.2.3 Tasks Test Configuration and Exploitation of Job Priorities Testing: WMS C++ API Testing: WMPROXY API. Job Priorities.
E N D
SA3 IFIC – report 22/05/2007 Álvaro Fernández IFIC (CSIC)
IFIC in SA3 • 12 PM • Gabriel Amoros (6PM) • Alvaro Fernandez (6PM) • Javier Sanchez • Officially • Task 3.2.3 • Tasks • Test Configuration and Exploitation of Job Priorities • Testing: WMS C++ API • Testing: WMPROXY API
Job Priorities • Still available PPS site using Maui/Torque to apply priorities and fair shares for Atlas jobs based on VOMS groups/roles. • with the recommendations of the priorities work group. • 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 • Check yaim-based configuration: • It was tested the yaim pre-release to check automatic configuration: yaim-3.0.1-6. • And the proper info providers: lcg-info-dynamic-scheduler-generic-2.0.1-1, and lcg-info-dynamic-schedules-pbs-1.6.1-1. • Some small problems were detected
Job Priorities • Problems/Issues • last tested yaim-3.0.1-16.3, to solve the configuration of DENY clauses (bug #25693: FQAn VOViews should be mutually exclusive) • Tested previously detected and solved bugs: • 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 • Continue helping testing and debugging issues • Test more complex scenarios: not only local policies
WMS C++ API • Objectives • Provide a test-suite to test the WMS C++API (client side) • check correctness • check completeness • Work was defined in Test plan (https://edms.cern.ch/document/674827/1 ) • Current implementation about 75 % on the test plan. • Available on cvs module org.glite.testsuites.wms-api • Built packages for glite3.0 • Built packages manually for glite3.1. • Worked on ETICS rpm generation: task #4412: build and provide the existing wms api tests module. • DID NOT SUCCEED (dependencies not working/updated)
Issues • Solved Bugs: • WMS CLI crashes when submitting job (if missing VOMS server cert at the WMS/LB node) (bug #14105, Integration Candidate) • WMS API deprecated for following releases: glite3.1 • While developing this testsuites some problems have arised regarding the implementation of the API. Some bugs were detected but will not be fixed: • bug #20863:WMS C++ API - glite::wmsui::api::Job::listMatchingCE method fails (Status: wont fix) • bug #22374: WMS C++ API: glite::wmsui::api::JobCollection::submit failure (Status: wont fix) • bug #22405: WMS C++ API: Interactive Jobs seg fault while submitting (Status: wont fix)
WMPROXY API • Web-services based Wmproxy api was co-existing and now deprecated ns-based. • We are starting moving implementation to the WMPROXY interface, which will be the one supported in the future. • Completedtask #4592: test plan for WMProxy API • Based on the original test plan (https://edms.cern.ch/file/608065/1/test_wms_api.pdf) to check that is compatible with the new interface. • Available at testplan_wmproxy_api.pdf • Completed certified patch#843( https://savannah.cern.ch/patch/?843) which deals with the python implementation of the WMPROXY api.
Current and future work • Started implementing the testsuite in Java ( and C++) • Will be at cvs modules • Org.glite.testsuites.wmproxy-api-java • Org.glite.testsuites.wmproxy-api-cpp • Will use Etics for building. Include dependencies in the system • Open issues: • bug #23004: yaim/glite-ui-config does not configure correct environment (PYTHONPATH, PERL5LIB, ...). Status: Open • Usage of api: Use of legacy python job-status commands • Usage of api: Transmission of files. • Api based testsuite ( not included in org.glite.testsuites.ctb) • How to include in the framework ( same based, ??) • Usage of junit, cppunit