> if jclouds only had careful tutorial or overview of builtin features :)
Valid point, indeed. My approach at present is to find a "similar" API (e.g. EC2 if it's XML, OpenStack if it uses optional components etc.), study the config and API/clients for those, and use that as a "template". Plus the mailing lists and IRC, obviously ;-) --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs/pull/12#issuecomment-21682914
