On 02/21/2013 01:50 AM, Dan Callaghan wrote:
I've just updated the harness API proposal:

http://beaker-project.org/dev/proposals/harness-api.html

Diff is here:

http://git.beaker-project.org/cgit/beaker-project.org/commit/?id=9e8ca6b6f7d90c7e6c4217bd2f657e76b07c6e87

I added "rejected features" and "deferred features" as per the 
discussions.

I also picked new environment variable names, and have reworded the 
proposal to reflect the idea that the "API" consists of certain 
environment variables set during installation, and certain HTTP 
resources made available by the lab controller. Hopefully that makes it 
clearer where I was coming from, with wanting to avoid the name 
HARNESS_API etc.

But of course I'm still open to suggestions about the names, or anything 
else.

Hi Dan,

Thanks for updating this.  Couple questions/comments.

first one is the following note about updating the task status:
"Note that if a task is aborted the entire recipe is aborted."

What about a localwatchdog?  Shouldn't that mark the task as aborted but continue on to the next task?


Second relates to Provisional period for the API.  Do you see any drawback to versioning the rest url?
For example: 
POST /v1/recipes/(recipe_id)/tasks/(task_id)/results/

This would be more flexible if we ever need to make changes, and both a v1 and v2 api could be made available at the same time.


Thanks

      

_______________________________________________
Beaker-devel mailing list
Beaker-devel@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/beaker-devel