Overview of WMS/LB API

Transcription

1 Overview of WMS/LB API Emidio Giorgio

2 Outline API vs. CLI Overview of WMProxy API Overview of Logging and Bookkeeping API Usage examples

3 API vs. CLI Users applications can be integrated on grid either using CLI users have to provide code invoking command line and handling outputs Pros faster deploy Cons tight dependency from command line behavior bad performance API calls to middleware services are embedded within applications Pros better perfomance real integration of application Cons slower deploy

4 CLI approach

5 CLI approach Your application Command line User Interface

6 CLI approach Your application Command line User Interface

7 CLI approach Your application Command line User Interface

8 CLI approach Your application Command line User Interface

9 CLI approach Your application Command line User Interface

10 CLI approach Your application Command line User Interface

11 CLI approach Your application Command line User Interface Output

12 API approach API

13 API approach Your application API

14 API approach Your application API

15 API approach Your application API

16 API approach Your application API

17 API approach Your application API Output

18 API Rub-up API are usually provided as libraries libraries have to be included when compiling the application code $ gcc -o simple-job-stat -I/opt/glite/include -L/opt/glite/ lib -lglite_lb_client_gcc32dbgpthr myappl.c calls to functions provided are inserted inside the application code // get the filesystem path to jdl-file from CLI string jdlpath=argv[argc -1]; jdl::ad ad; // declare a new ClassAd // initialize the ClassAd with file content ad.fromfile (jdlpath); // convert AD to String and save it in jdlstring string jdlstring (ad.tostring()); /* call joblistmatch */ vector < pair < string,long > > matchingces = joblistmatch(jdlstring, delegationid, &cfg);

19 WMS API glite 3.1 $ rpm -qa grep -i glite-wms grep api glite-wms-wmproxy-api-python slc4 glite-wms-wmproxy-api-java glite-wms-wmproxy-api-cpp slc4 $ rpm -ql glite-wms-wmproxy-api-cpp slc4 /opt/glite/include/glite/wms/wmproxyapi /opt/glite/include/glite/wms/wmproxyapi/wmproxy_api.h /opt/glite/include/glite/wms/wmproxyapi/wmproxy_api_utilities.h /opt/glite/lib/libglite_wms_wmproxy_api_cpp.a /opt/glite/lib/libglite_wms_wmproxy_api_cpp.so /opt/glite/lib/libglite_wms_wmproxy_api_cpp.so.0 [cut...] Allow to list-match and submit a jdl file output retrieve more details during practicals JDL API are requested too Have a look to the included header files to check out how to improve functionalities and info provided

20 LB API Not directly deployed same libraries used by command lines are included Only in C For each query to LB, expressed through the job ID, a struct is returned, and filled with all the information about the queried job Users inspect the returned struct in order to get infomations about the job Challenge Improve the output provided from the example providing more info? Have a look to edg_wll_queryattr within /opt/glite/include/glite/lb/consumer.h to see what can be obtained from a query

21 Material Working examples References Google...