RE: [Myexperiment-discuss] API questions: runners, Remote Execution Service

[David R Newman]

Hi Wladmir,

 

Question 1:

When you set a runner as being owned by a group, it will not appear in the XML for you as a user as that only lists contributions (e.g. workflows, runners, etc.) owned by you, annotations (e.g. tags, comments, etc.) created by you and friends, memberships, etc.  However, thanks for bringing this to our attention, as the correct behaviour should be to list it under runners in the group XML.  The REST API should be updated shortly to do provide this.

 

Question 2:

I will have to leave the details about the implementation status of the posting to the Jobs API to Don Cruickshank.  In theory you should be able to access a listing of all runners you as a user have access to (runners.xml) and individual XML for each of these runners (runner.xml?id=n).  However, I believe there may be a issue with runners.xml that needs resolving first.  The one problem with your plan of circumnavigating creating a myExperiment job, is that runners have a password that you cannot get back through the REST API for obvious reasons.  If you could get hold of the password separately then you could do something like you suggest.  The purpose of runners in myExperiment is to allow you to automatically upload workflow executions.  The purpose of being able to make it owned by a  group is to support a proxy facility where one person can open up a runner to multiple users without having to share the password.

 

Hope this helps,

 

David Newman

 

From: address@hidden [mailto:address@hidden On Behalf Of Wladimir Mufty
Sent: 02 December 2010 15:58
To: address@hidden
Subject: [Myexperiment-discuss] API questions: runners, Remote Execution Service

 

Hello,

I had 2 questions about the API:



Question 1: Shared group runners

Is it correct that the shared “group” runners are not returned with a request to:

http://sandbox.myexperiment.org/user.xml?id=[ID user x]&elements=workflows

It seems that it only provides the personal runner(s) for that specific user.

Question 2: Taverna server 1.7

We are using the Remote Execution Service on a (private) machine on the internet.

We would like to make use of this Remote Execution Service through the use of API / REST calls.

 On MyExperiment you can check the runners API for available runners, in continuation of that it is (or should) be possible to create a “job” through the Jobs API.

 - Is the Jobs API available, can we run a selected workflow through a job on a runner-machine?

- Is it possible to skip the creation of a Job and directly post a workflow to the Remote Execution Service API?

 API scenario:

1a. Get workflows MyExperiment user X (http://sandbox.myexperiment.org/user.xml?id=[ID user x]&elements=workflows)

1b. Get available MyExperiment  runners user X (http://sandbox.myexperiment.org/runner.xml?id=[runnerid])

2. Post selected workflow to available runner-machine, the Remote Execution Service. Direct! Not via MyExperiment or a MyExperiment Job.

3. Check status and link to result set on runner-machine.

 Please let me know if this scenario is already possible or will be possible in the near (or not so near) future.

 

Kind Regards,

 

Wladimir Mufty

SURFnet