Hello Andrew, Thanks for the suggestion. Andrei Savu (we work together) also suggested I go with jclouds but I wanted to hear what the community has to say about this. We're building an app that can reliably provision 10's 100's of machines across cloud providers. Right now it's actually a contest, winner gets a present from the looser. I have to implement Cloudstack and he's got Amazon.
Good luck with your talk tomorrow, maybe you could share the slides/presentation afterwords. Thanks, On Fri, Nov 30, 2012 at 8:45 PM, Andrew Bayer <andrew.ba...@gmail.com> wrote: > If I can toot my own horn (as the current de facto maintainer of the jclouds > CloudStack work), I'd strongly suggest using jclouds. It uses the real > CloudStack API rather than the AWS shim, and gives you all the bells and > whistles, retries, abstractions etc from jclouds. You can also use the > CloudStack API directly (I.e., not through the jclouds abstraction layer) if > you need access to CloudStack-specific functionality. I'm actually going to > be giving a talk about jclouds and CloudStack tomorrow here at the CloudStack > Collaboration Conference. =) > > A. > > > > On Nov 30, 2012, at 2:57 AM, Ioan Eugen Stan <stan.ieu...@gmail.com> wrote: > >> Hello Cloudstack, >> >> I've just joined the community. I'm working on a project (soon to be >> proposed in the ASF Incubator) that aims to make the task of >> provisioning VM's on cloud infrastructure very easy. I've just started >> working on the Cloudstack driver and I need your help picking the >> client API library. Which one should I pick? We are currently using >> Cloudstack 3.0, but also thinking about the future. >> >> I know about: >> - jclouds support for cloudstack >> - cloudbridge Amazon API layer - so maybe Amazon SDK or jclouds again >> - cloudstack API? >> >> Which one is more suitable for now and which one do you think will be >> developed further in the future? >> >> Thanks, >> >> -- >> Ioan Eugen Stan / CTO / http://axemblr.com -- Ioan Eugen Stan / CTO / http://axemblr.com
