On Thu, Oct 8, 2009 at 9:13 PM, Hugh O. Brock hbrock@redhat.com wrote:
Yeah standard procedure is to post patches and get somebody to ack them, then commit. We have not been enforcing that strictly thus far in the interest of getting things up and running, but it's more important now. Great to see the rackspace driver in though! Anyone test it yet?
--Hugh
Only me ;) I didn't send around a patch for rackspace support as each driver is (currently) its own repo.
Pretty simple as they had a REST styled API, which supported application/json content type, which made reading it into Ruby just a doddle (which means easy, I think...).
Just wanted to update the docs to reflect it.
I do need to tweak the framework to have some standard error we can throw to percolate up to the user that something is badly wrong (probably programmer error !).