Line: 1 to 1 | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
CREAM client API for Python | ||||||||||
Line: 36 to 33 | ||||||||||
| ||||||||||
Changed: | ||||||||||
< < |
| |||||||||
> > |
| |||||||||
| ||||||||||
Line: 80 to 70 | ||||||||||
| ||||||||||
Changed: | ||||||||||
< < | The API architecture is founded on a super and abstract class <a target="_blank" href="http://www.italiangrid.org/CREAM-CLIENT-API/classglite_1_1ce_1_1cream__client__api_1_1soap__proxy_1_1AbsCreamProxy.html" title="AbsCreamProxy">AbsCreamProxy that exposes 3 relevant public methods: <span style="font-family: 'Courier New', courier, monaco, monospace; font-size: 16px;"><a target="_blank" href="http://www.italiangrid.org/CREAM-CLIENT-API/classglite_1_1ce_1_1cream__client__api_1_1soap__proxy_1_1AbsCreamProxy.html#1701485b30de eb2b0b6444286d1d6126" title="AbsCreamProxy.setCredential(...)">AbsCreamProxy.setCredential(...), <span style="font-family: 'Courier New', courier, monaco, monospace; font-size: 16px;"><a target="_blank" href="http://www.italiangrid.org/CREAM-CLIENT-API/classglite_1_1ce_1_1cream__client__api_1_1soap__proxy_1_1AbsCreamProxy.html#4dd4f8490789 fed0bce2b7b971c3aa3f" title="AbsCreamProxy.setConnectionTimeout(...)">AbsCreamProxy.setConnectionTimeout(...), <a target="_blank" href="http://www.italiangrid.org/CREAM-CLIENT-API/classglite_1_1ce_1_1cream__client__api_1_1soap__proxy_1_1AbsCreamProxy.html#8cf7a83ee8e3 2da416a5481879e68a6f" title="AbsCreamProxy.execute(...)">AbsCreamProxy.execute(...). The method <span style="font-family: 'Courier New', courier, monaco, monospace; font-size: 16px;">execute(...) is pure virtual. There're several <a target="_blank" href="http://www.italiangrid.org/CREAM-CLIENT-API/classglite_1_1ce_1_1cream__client__api_1_1soap__proxy_1_1AbsCreamProxy.html" title="AbsCreamProxy">AbsCreamProxy's subclasses, one for each operation mentioned above: CreamProxy _Start, CreamProxy _Register, | |||||||||
> > | The API architecture is founded on a super and abstract class AbsCreamProxy that exposes 3 relevant public methods: AbsCreamProxy.setCredential(...), AbsCreamProxy.setConnectionTimeout(...) , AbsCreamProxy.execute(...) . The method execute(...) is pure virtual. There're several AbsCreamProxy 's subclasses, one for each operation mentioned above: CreamProxy _Start, CreamProxy _Register, | |||||||||
CreamProxy _Cancel, and so on. Each of them implements its own execute(...) method, specific for the kind of operation the subclass itself represents; this implementation is responsible for the connection to the remote Web Service (CREAM), sending the SOAP request, receiving the SOAP response and unserializing it and hides the user from any SOAP communication and authentication detail. All the subclasses have | ||||||||||
Changed: | ||||||||||
< < | protected constructors, so the developer cannot directly create a subclass, but she/he must use a special factory named <a target="_blank" href="http://www.italiangrid.org/CREAM-CLIENT-API/classglite_1_1ce_1_1cream__client__api_1_1soap__proxy_1_1CreamProxyFactory.html" title="CreamProxyFactory">CreamProxyFactory. For each operation the factory has a make_<OPERATION_NAME>(...) method. The factory's 'make' methods returns an object of one of the classes subclassing <a target="_blank" href="http://www.italiangrid.org/CREAM-CLIENT-API/classglite_1_1ce_1_1cream__client__api_1_1soap__proxy_1_1AbsCreamProxy.html" title="AbsCreamProxy">AbsCreamProxy. The 'make' methods take different parameters depending on the kind of operation is performed by | |||||||||
> > | protected constructors, so the developer cannot directly create a subclass, but she/he must use a special factory named CreamProxyFactory . For each operation the factory has a make_<OPERATION_NAME>(...) method. The factory's 'make' methods returns an object of one of the classes subclassing AbsCreamProxy . The 'make' methods take different parameters depending on the kind of operation is performed by | |||||||||
the returned object. | ||||||||||
Changed: | ||||||||||
< < | When the user got an object of class subclassing <a target="_blank" href="http://www.italiangrid.org/CREAM-CLIENT-API/classglite_1_1ce_1_1cream__client__api_1_1soap__proxy_1_1AbsCreamProxy.html" title="AbsCreamProxy">AbsCreamProxy class she/he has to invoke the setCredential(...) method in order to set the authentication | |||||||||
> > | When the user got an object of class subclassing AbsCreamProxy class she/he has to invoke the setCredential(...) method in order to set the authentication | |||||||||
credentials, optionally invoke the setConnectionTimeout(...) in order to set a maximum socket timeout for the connections with the CREAM service, and then must invoke execute(...) to actually communicate with the service (send SOAP request, receive and parse SOAP response). It is clear that the developer has to know nothing about subclasses: she/he just uses factory's make methods and the two methods | ||||||||||
Changed: | ||||||||||
< < | setCredential(...) and execute(...); then the subclasses are not documented at all. The API documentation only describes the <a target="_blank" href="http://www.italiangrid.org/CREAM-CLIENT-API/classglite_1_1ce_1_1cream__client__api_1_1soap__proxy_1_1AbsCreamProxy.html" title="AbsCreamProxy">AbsCreamProxy, the factory and the data structures to pass as argument of the 'make' methods of the factory. At the end, when using the Cpp API the user had to 'del' the object of <a target="_blank" href="http://www.italiangrid.org/CREAM-CLIENT-API/classglite_1_1ce_1_1cream__client__api_1_1soap__proxy_1_1AbsCreamProxy.html" title="AbsCreamProxy">AbsCreamProxy class in order to free the heap-memory that the factory allocated. | |||||||||
> > | setCredential(...) and execute(...); then the subclasses are not documented at all. The API documentation only describes the AbsCreamProxy , the factory and the data structures to pass as argument of the 'make' methods of the factory. At the end, when using the Cpp API the user had to 'del' the object of AbsCreamProxy class in order to free the heap-memory that the factory allocated. | |||||||||
Step by step Job Submission explanationProxy DelegationIn order to register a job, the user must previously delegate a proxy into the remote CREAM CE service. The procedure is a matter of a few steps: | ||||||||||
Changed: | ||||||||||
< < |
| |||||||||
> > |
| |||||||||
| ||||||||||
Changed: | ||||||||||
< < | Download the example code in attach ( tryDelegate.py ) | |||||||||
> > | Download the example code in attach ( tryDelegate.py ) | |||||||||
and build it with the instructions described above.
Job RegistrationThe steps for the JobRegister operation are:
| ||||||||||
Changed: | ||||||||||
< < | href="http://www.italiangrid.org/CREAM-CLIENT-API/classglite_1_1ce_1_1cream__client__api_1_1soap__proxy_1_1JobDescriptionWrapper.html">Job DescriptionWrapper object for each job to submit to the CREAM CE | |||||||||
> > |
| |||||||||
| ||||||||||
Changed: | ||||||||||
< < |
| |||||||||
> > |
| |||||||||
| ||||||||||
Changed: | ||||||||||
< < | The input and output arguments of the <a href="http://www.italiangrid.org/CREAM-CLIENT-API/classglite_1_1ce_1_1cream__client__api_1_1soap__proxy_1_1CreamProxyFactory.html#81cc3d71 8ca6b6a7424a7e9ea219bd5d">CreamProxyFactory.make_CreamProxyRegister(...) are a bit more complicated than in the case of the Proxy | |||||||||
> > | The input and output arguments of the CreamProxyFactory.make_CreamProxyRegister(...) are a bit more complicated than in the case of the Proxy | |||||||||
Delegation. As described in the API reference, the input and output arguments are pointers to: | ||||||||||
Changed: | ||||||||||
< < |
| |||||||||
> > | ||||||||||
In Cpp API they are typedef for (respectively):
| ||||||||||
Line: 174 to 149 | ||||||||||
| ||||||||||
Changed: | ||||||||||
< < | based on the boost::tuple library. Each | |||||||||
> > | based on the boost::tuple library. Each | |||||||||
JobDescriptionWrapper object is built with a JobDescription identifier (an arbitrary string chosen by user) and other parameters that can | ||||||||||
Changed: | ||||||||||
< < | been seen in the example source code tryRegister.py. | |||||||||
> > | been seen in the example source code tryRegister.py . | |||||||||
After the invocation of the execute(...) method, the second argument (passed to the CreamProxyFactory.make_CreamProxyRegister(...)
function as output parameter) will be filled as follows:
| ||||||||||
Changed: | ||||||||||
< < |
| |||||||||
> > |
| |||||||||
| ||||||||||
Changed: | ||||||||||
< < | As shown in the example source code tryRegister.py, a | |||||||||
> > | As shown in the example source code tryRegister.py , a | |||||||||
mandatory argument is autostart. In the example it is set to false; this means that the job is ONLY REGISTERED and NOT STARTED. Below it is explained the usefulness of autostart set to false. If she/he needs to start the job immediately after registration she/he can set to true the autostart parameter. An array of properties (implemented as a map of string pairs, i.e. couples key -> value ) is embedded in | ||||||||||
Line: 194 to 174 | ||||||||||
in the CE the user can send its InputSandbox to, and name 'CREAMInputSandboxURI' (see again the example source code).
| ||||||||||
Changed: | ||||||||||
< < | href="https://raw.github.com/maciex/pyCream/master/examples/tryMultipleRegister.py">here | |||||||||
> > |
| |||||||||
Job startIn the previous example, jobs are simply registered in the CREAM CE (autostart is set to false). This is useful if the user needs to do | ||||||||||
Line: 203 to 182 | ||||||||||
explicitly start a job the user must:
| ||||||||||
Changed: | ||||||||||
< < |
| |||||||||
> > |
| |||||||||
| ||||||||||
Line: 221 to 193 | ||||||||||
Cancelling, Suspending, Resuming and Purging jobsThe code for these four operations is basically the same. The user has to | ||||||||||
Changed: | ||||||||||
< < |
| |||||||||
> > |
| |||||||||
Like in the JobStart case, to cancel/suspend/resume/purge all her/his jobs, the user has to use an empty list(stdVectorJobIdWrapper) of JobIdWrapper objects as argument of the JobFilterWrapper's costructor. | ||||||||||
Changed: | ||||||||||
< < | The source code example is here. Please note that it is | |||||||||
> > | The source code example is here . Please note that it is | |||||||||
only for JobCancel operation; adapting it for the other three operations is straightforward.
Listing jobs in a CREAM CE | ||||||||||
Changed: | ||||||||||
< < | The code for listing all the jobs submitted to a CREAM CE is very simple; a few simple parameters are needed for the factory <a href="http://www.italiangrid.org/CREAM-CLIENT-API/classglite_1_1ce_1_1cream__client__api_1_1soap__proxy_1_1CreamProxyFactory.html#55c63ef9 33f274bbcfa7f29067043b7e">CreamProxyFactory.makeCreamProxyList(...). A look at the source code should be enough to understand what the user has to do. | |||||||||
> > | The code for listing all the jobs submitted to a CREAM CE is very simple; a few simple parameters are needed for the factory CreamProxyFactory.makeCreamProxyList(...) . A look at the source code should be enough to understand what the user has to do. | |||||||||
Getting Information about jobs submitted to a CREAM CEA user can invoke two operations to get information on one or more jobs submitted to a CREAM CE: JobInfo and JobStatus. The latter is | ||||||||||
Line: 264 to 228 | ||||||||||
query) and with other constraints to select a particular set of jobs (see the JobFilterWrapper documentation). As usual a user can query for the states of all her/his jobs; this can be achieved by using an empty vector of JobIdWrapper objects as | ||||||||||
Changed: | ||||||||||
< < | argument of the JobFilterWrapper's costructor. See the <a href="http://www.italiangrid.org/CREAM-CLIENT-API/classglite_1_1ce_1_1cream__client__api_1_1soap__proxy_1_1CreamProxyFactory.html#10f1cbc0 06fd1a9eaba6beace0a46c19">CreamProxyFactory.make_CreamProxyStatus(...) and JobStatu sWrapper documentation for more details about the structure of the information returned by CREAM. As usual the example code is the best way to explain how | |||||||||
> > | argument of the JobFilterWrapper's costructor. See the CreamProxyFactory.make_CreamProxyStatus(...) and JobStatusWrapper documentation for more details about the structure of the information returned by CREAM. As usual the example code is the best way to explain how | |||||||||
it works.
Slow info query (JobInfo)To get complete information about jobs the user must invoke the remote call JobInfo. The procedure is much similar to the fast call | ||||||||||
Changed: | ||||||||||
< < | JobStatus: the user has to prepare a JobFilterWrapper object to select jobs and filters; then the result will be put in a JobInfoWra pper structure instead of a JobStatusWrapper. The data structure containing the output of the JobInfo operation is very similar to that one for the JobStatus operation. See the <a href="http://www.italiangrid.org/CREAM-CLIENT-API/classglite_1_1ce_1_1cream__client__api_1_1soap__proxy_1_1CreamProxyFactory.html#c89548fc ca3ded7dd48c2c31745cf8eb">CreamProxyFactory.make_CreamProxyInfo(...) and JobInfoWrapper documentation for more details about the | |||||||||
> > | JobStatus: the user has to prepare a JobFilterWrapper object to select jobs and filters; then the result will be put in a JobInfoWrapper structure instead of a JobStatusWrapper. The data structure containing the output of the JobInfo operation is very similar to that one for the JobStatus operation. See the CreamProxyFactory.make_CreamProxyInfo(...) and JobInfoWrapper documentation for more details about the | |||||||||
structure of the information returned by CREAM. | ||||||||||
Changed: | ||||||||||
< < | Example source code. | |||||||||
> > | Example source code. | |||||||||
Enabling and disabling the Job Submission ServiceDepending on the role of the user, she/he can enable/disable the job submission on a remote CREAM CE. The code is so simple that, as | ||||||||||
Changed: | ||||||||||
< < | usual, the example speaks for itself. Relevant API documentation is clearly the factory method <a href="http://www.italiangrid.org/CREAM-CLIENT-API/classglite_1_1ce_1_1cream__client__api_1_1soap__proxy_1_1CreamProxyFactory.html#4d9f5de3 f978ed3425540d091c5a0455">CramProxyFactory.make_CreamProxyAcceptNewJobSubmissions(...). | |||||||||
> > | usual, the example speaks for itself. Relevant API documentation is clearly the factory method CramProxyFactory.make_CreamProxyAcceptNewJobSubmissions(...) . | |||||||||
Renewing a Delegated Proxy | ||||||||||
Line: 298 to 267 | ||||||||||
delegation; this identifier will be used to register jobs. But the proxy are not valid forever. At some point the delegated proxy must be renewed. The procedure is as simple as in the delegation case. The user has just to put the delegation identifier string into the factory method that creates the proper AbsCreamProxy subclass and invoke, as usual, setCredential(...) and execute(...). Taking a look at the | ||||||||||
Changed: | ||||||||||
< < | example source code is the fastest way to understand this very simple procedure. Relevant API documentation is clearly the factory method <a href="http://www.italiangrid.org/CREAM-CLIENT-API/classglite_1_1ce_1_1cream__client__api_1_1soap__proxy_1_1CreamProxyFactory.html#7aac61bb 1e0c482358264c362116e62f">CramProxyFactory.make_CreamProxy_ProxyRenew(...). | |||||||||
> > | example source code is the fastest way to understand this very simple procedure. Relevant API documentation is clearly the factory method CramProxyFactory.make_CreamProxy_ProxyRenew(...) . | |||||||||
Querying job status eventsQueryEvent is a convenient CREAM's operation that returns a selected range of particular events. At the moment in the CREAM framework an | ||||||||||
Line: 319 to 290 | ||||||||||
Finally, the filter related to job's states simply select those events that carry a job status that is present in a list specified by the user. | ||||||||||
Changed: | ||||||||||
< < | As usual, in order to perform a QueryEvent the user must obtain a pointer to an AbsCreamProxy object by mean of <a href="http://www.italiangrid.org/CREAM-CLIENT-API/classglite_1_1ce_1_1cream__client__api_1_1soap__proxy_1_1CreamProxyFactory.html#1f2d95ea 6a37e8ffef7e137e00009f72">CreamProxyFactory.make_CreamProxy_QueryEvent(...), invoke setCredential(...) and execute(...) methods on it, and delete it. The invocation of execute(...) will fill up a list of EventWrapper pointers (that is an argument of the CreamProxyFactory.make_CreamProxy_QueryEvent function). Please see the example source code to understand how | |||||||||
> > | As usual, in order to perform a QueryEvent the user must obtain a pointer to an AbsCreamProxy object by mean of CreamProxyFactory.make_CreamProxy_QueryEvent(...) , invoke setCredential(...) and execute(...) methods on it, and delete it. The invocation of execute(...) will fill up a list of EventWrapper pointers (that is an argument of the CreamProxyFactory.make_CreamProxy_QueryEvent function). Please see the example source code to understand how | |||||||||
to use the above stuff.
Getting Service Information from a deployed CREAM CE running service | ||||||||||
Changed: | ||||||||||
< < | This remote operation is very simple; the factory <a href="http://www.italiangrid.org/CREAM-CLIENT-API/classglite_1_1ce_1_1cream__client__api_1_1soap__proxy_1_1CreamProxyFactory.html#d69bbf4a 2a8e520704c7ff7348024a4d">CreamProxyFactory.make_CreamProxyServiceInfo(...) just needs a simple parameter that is a Servic eInfoWrapper object and a verbosity; ServiceInfoWrapper exposes methods to obtain information on the CREAM service which are be | |||||||||
> > | This remote operation is very simple; the factory CreamProxyFactory.make_CreamProxyServiceInfo(...) just needs a simple parameter that is a ServiceInfoWrapper object and a verbosity; ServiceInfoWrapper exposes methods to obtain information on the CREAM service which are be | |||||||||
self-explanatory. | ||||||||||
Changed: | ||||||||||
< < | Example source code. | |||||||||
> > | Example source code . | |||||||||
Line: 1 to 1 | ||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||
Changed: | ||||||||||||||||||||||||||||||||||||||||||||||
< < | CREAM client API for Python | |||||||||||||||||||||||||||||||||||||||||||||
> > | CREAM client API for Python | |||||||||||||||||||||||||||||||||||||||||||||
Maciej Sitarz created a CREAM Client API for Python language. | ||||||||||||||||||||||||||||||||||||||||||||||
Line: 10 to 10 | ||||||||||||||||||||||||||||||||||||||||||||||
If you have any problems or questions regarding building/installation/usage of the pyCream module, you can contact Maciej via github or via e-mail (macieksitarz AT wp DOT pl). | ||||||||||||||||||||||||||||||||||||||||||||||
Added: | ||||||||||||||||||||||||||||||||||||||||||||||
> > | CREAM Client development tutorialPreliminaries: build machine configurationBefore developing a CREAM's Py CLI you must configure properly a SL5_64bit machine. The prerequisites are the same as for Cpp Client. Additional requrements are: * python (tested with version 2.7) * boost (tested with version 1.45)Cpp API vs. Python API -- differencesSTL collectionsAll of the STL objects passed to the API calls need to be of one of the wrapped types. Here's a table of those corresponding types.
Freeing memoryWhen using the Cpp API the user had to delelte the pointer in order to free the heap-memory that the AbsCreamProxy factory allocated. In Python one can use 'del' statement, probably it's not needed because the memory should be cleaned by Python's garbage collector (need to check that somehow!).CLI DevelopmentBuilding of the example source code (see attachments)In the attachments you can find small examples that explain how to use the CREAM Client API Python.Quick overview of the APICurrently, the Python API implements the following operations:
Step by step Job Submission explanationProxy DelegationIn order to register a job, the user must previously delegate a proxy into the remote CREAM CE service. The procedure is a matter of a few steps:
Job RegistrationThe steps for the JobRegister operation are:
Job startIn the previous example, jobs are simply registered in the CREAM CE (autostart is set to false). This is useful if the user needs to do something between job registration and job start (e.g.: sending an input sandbox in the remote path specified by the CREAM CE). To explicitly start a job the user must:
Cancelling, Suspending, Resuming and Purging jobsThe code for these four operations is basically the same. The user has to
Listing jobs in a CREAM CEThe code for listing all the jobs submitted to a CREAM CE is very simple; a few simple parameters are needed for the factory <a href="http://www.italiangrid.org/CREAM-CLIENT-API/classglite_1_1ce_1_1cream__client__api_1_1soap__proxy_1_1CreamProxyFactory.html#55c63ef9 33f274bbcfa7f29067043b7e">CreamProxyFactory.makeCreamProxyList(...). A look at the source code should be enough to understand what the user has to do.Getting Information about jobs submitted to a CREAM CEA user can invoke two operations to get information on one or more jobs submitted to a CREAM CE: JobInfo and JobStatus. The latter is quicker but provides less information than the former. In both cases the user must prepare a JobFilterWrapper object that collects all the identifier strings of the jobs to query and the conditions the jobs must satisfy in order to be included in the result. For example a user might need the query status of all jobs submitted between 8:00am and 15:00am of a particular day (if they were not purged out yet). Or she/he might need information on all the jobs that are in the "RUNNING" OR "DONE-OK" status... and so on. Please see the documentation of JobFilterWrapper to see what filters a user can define.Fast info query (JobStatus)With the invocation of the JobStatus remote operation CREAM will return a minimal set of information about the jobs: the current status of the job, the timestamp of the last status change, the exit code of the job and the failure reason (if the job finished or aborted). To query the states of some jobs, the user must prepare a JobFilterWrapper object and fill it with JobIdWrapper objects (one for each job to query) and with other constraints to select a particular set of jobs (see the JobFilterWrapper documentation). As usual a user can query for the states of all her/his jobs; this can be achieved by using an empty vector of JobIdWrapper objects as argument of the JobFilterWrapper's costructor. See the <a href="http://www.italiangrid.org/CREAM-CLIENT-API/classglite_1_1ce_1_1cream__client__api_1_1soap__proxy_1_1CreamProxyFactory.html#10f1cbc0 06fd1a9eaba6beace0a46c19">CreamProxyFactory.make_CreamProxyStatus(...) and JobStatu sWrapper documentation for more details about the structure of the information returned by CREAM. As usual the example code is the best way to explain how it works.Slow info query (JobInfo)To get complete information about jobs the user must invoke the remote call JobInfo. The procedure is much similar to the fast call JobStatus: the user has to prepare a JobFilterWrapper object to select jobs and filters; then the result will be put in a JobInfoWra pper structure instead of a JobStatusWrapper. The data structure containing the output of the JobInfo operation is very similar to that one for the JobStatus operation. See the <a href="http://www.italiangrid.org/CREAM-CLIENT-API/classglite_1_1ce_1_1cream__client__api_1_1soap__proxy_1_1CreamProxyFactory.html#c89548fc ca3ded7dd48c2c31745cf8eb">CreamProxyFactory.make_CreamProxyInfo(...) and JobInfoWrapper documentation for more details about the structure of the information returned by CREAM. Example source code.Enabling and disabling the Job Submission ServiceDepending on the role of the user, she/he can enable/disable the job submission on a remote CREAM CE. The code is so simple that, as usual, the example speaks for itself. Relevant API documentation is clearly the factory method <a href="http://www.italiangrid.org/CREAM-CLIENT-API/classglite_1_1ce_1_1cream__client__api_1_1soap__proxy_1_1CreamProxyFactory.html#4d9f5de3 f978ed3425540d091c5a0455">CramProxyFactory.make_CreamProxyAcceptNewJobSubmissions(...).Renewing a Delegated ProxyTo register a job to a CREAM CE a client must first delegate a proxy to the CE and save an identifier string associated with this delegation; this identifier will be used to register jobs. But the proxy are not valid forever. At some point the delegated proxy must be renewed. The procedure is as simple as in the delegation case. The user has just to put the delegation identifier string into the factory method that creates the proper AbsCreamProxy subclass and invoke, as usual, setCredential(...) and execute(...). Taking a look at the example source code is the fastest way to understand this very simple procedure. Relevant API documentation is clearly the factory method <a href="http://www.italiangrid.org/CREAM-CLIENT-API/classglite_1_1ce_1_1cream__client__api_1_1soap__proxy_1_1CreamProxyFactory.html#7aac61bb 1e0c482358264c362116e62f">CramProxyFactory.make_CreamProxy_ProxyRenew(...).Querying job status eventsQueryEvent is a convenient CREAM's operation that returns a selected range of particular events. At the moment in the CREAM framework an Event is a job's status change; in future an evolved version of CREAM could put different kind of information inside an event. A user that invokes a QueryEvent on a CREAM CE, receives all her/his jobs's status changes. The query has three filters:
Getting Service Information from a deployed CREAM CE running serviceThis remote operation is very simple; the factory <a href="http://www.italiangrid.org/CREAM-CLIENT-API/classglite_1_1ce_1_1cream__client__api_1_1soap__proxy_1_1CreamProxyFactory.html#d69bbf4a 2a8e520704c7ff7348024a4d">CreamProxyFactory.make_CreamProxyServiceInfo(...) just needs a simple parameter that is a Servic eInfoWrapper object and a verbosity; ServiceInfoWrapper exposes methods to obtain information on the CREAM service which are be self-explanatory. Example source code. | |||||||||||||||||||||||||||||||||||||||||||||
-- MassimoSgaravatto - 2011-07-30 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Added: | ||||||||
> > |
CREAM client API for PythonMaciej Sitarz created a CREAM Client API for Python language. ThepyCream project is available on github (https://github.com/maciex/pyCream), so anyone can download, use it or participate in development. It's GPLv3
licensed.
If you have any problems or questions regarding building/installation/usage of the pyCream module, you can contact Maciej via github or via e-mail (macieksitarz AT wp DOT pl).
-- MassimoSgaravatto - 2011-07-30 |