Hey,
Eoghan and I are going to give a shot at this agile sprint malarky
Here's our focus for the next two weeks:
https://fedorahosted.org/rhevm-api/wiki/Sprint1
Cheers,
Mark.
= Sprint 1 =
Starting Friday April 23rd, finishing Thursday May 7th.
The basic theme is to finalize some of the gnarly [wiki:Design_Questions
API design issues] while also making a big improvement in the functional
coverage of the API.
== Mark's Tasks ==
1. Expand the API coverage so that, given a fresh RHEV-M install, the
following is possible:
* Add a host
* Create a storage domain
* Install a VM
* Create a template from that VM
2. Resolve the question of how we want to pass parameters to actions
3. Re-jigger our RHEV-M install so that Eoghan can use it remotely
== Eoghan's Tasks ==
1. Figure out what we're going to do about async operations:
* Should actions have an async parameter?
* If so, when POSTing to a collection, how to make the creation
async?
* An async operation will return a URI to poll; what will a GET
on that return?
* Once an async operation is completed, do we need to worry about
purging the record of that completion at some point?
* Should we integrate operation completions with the audit/event
log?
2. Decide on {{{<vm href="..."/>}}} versus {{{<link
rel="host"
href="..."/>}}}
3. Make the dummy and powershell implementations simple servlets
rather than EJBs
4. Return an error if the client tries to change an object UUID.
Requires thinking about how we should handle errors.
5. Decide what our media types should be and add support for them.