On Fri, Jan 25, 2013 at 5:04 PM, David Lutterkort <[email protected]> wrote: > On Fri, 2013-01-25 at 15:44 -0500, Chip Childers wrote: >> First, I believe that the documentation is clear enough about how to >> add a driver (and there are plenty of good examples). I'm sure I'll >> have questions as I go, but I think there's a good starting point. > > Besides the mailing list, we are also on #deltacloud in freenode - feel > free to ask questions there, too. >
Thanks. I'll jump in there as I have questions. >> Second, in order to make it easier on myself, I just published a >> cloudstack_ruby_client gem [1] that I'm licensing via ASLv2 (source at >> [2]). My plan is to keep that up to date, and actually use the >> Deltacloud provider development as a way to fully test the client >> library. Are there any objections to me including this as a >> dependency? > > That's the pattern we are following with most of our drivers these days: > all the heavy lifting happens in the client gem, and the driver itself > is just glue between the client gem and the rest of Deltacloud. So this > is actually the best way to structure a driver. > Great - Glad I started there then. > For examples, it's probably best to look at the mock driver since that > has a pretty clear separation between client and glue code (though the > client for that lives right next to the driver) and the EC2 driver since > that is the oldest and most worked-over driver. The mock driver seems to be the best place for me so far. I'm using it as the starting point, and modifying it as I go to switch from the mocked responses to the cloudstack client calls. -chip
