Hi, Kevin. Andrew's experience seems to gel with that, so far. Only a quirk about listAll, which seems harmless.
http://code.google.com/p/jclouds/issues/detail?id=927 -A On Fri, May 18, 2012 at 5:09 PM, Kevin Kluge <kevin.kl...@citrix.com> wrote: > Adrian, do you have specific list calls that are not backwards compatible > from 3.0.x to 2.2.x? I thought we had made the end-user API backwards > compatible (assuming IDs are strings...). > > -kevin > >> -----Original Message----- >> From: fernc...@gmail.com [mailto:fernc...@gmail.com] On Behalf Of >> Adrian Cole >> Sent: Friday, May 18, 2012 12:04 PM >> To: cloudstack-dev@incubator.apache.org >> Subject: Re: jclouds support for 3.0 >> >> I've noticed Andrew Bayer working on this today on freenode irc #jclouds >> >> Apparently, the shift of ids from numeric to opaque string means we have a >> choice of either apologizing and changing 2.x code to use strings or a >> potentially massive copy paste into a new version tree. >> >> Also he noted some list ops are incompatible, but that's easier than the >> domain model. >> >> -A >> On May 18, 2012 10:36 AM, "Chiradeep Vittal" <chiradeep.vit...@citrix.com> >> wrote: >> >> > Anybody using jclouds to interact with CloudStack? >> > Currently jclouds does not support CloudStack 3.0 I've raised an >> > enhancement request [1] >> > >> > If you are interested (or can help out jclouds with this), please >> > contribute. >> > >> > My own interest is in being able to use Apache Whirr to launch Apache >> > Hadoop on CloudStack 3.0 >> > >> > [1] http://code.google.com/p/jclouds/issues/detail?id=927 >> > >> > >> > -- >> > Chiradeep >> > >> >
