Good morning. I've pushed the changes to my repo (https://github.com/carlosgarciaibanez/jclouds-labs.git), into the PATCHES_TRANSPORT_2.6 branch (forked from the 1.7.2-SNAPSHOT). I've not run the live tests yet, because I have to figure out the parameters to set in the filters.properties (I'm asking our Operations team for this information). So please, don't take the changes too seriously, since the only thing I've checked is that my software still runs :) Right now I'm working on the VM update operation to pass the new forceVDCLimits flag, which cannot be provided yet. One thing to take into account: the version 2.6 of the transport components is compiled with Java 7, so I had to change my running environment accordingly. Any comments or suggestions are welcome. Thanks again!
From: Ignasi Barrera [mailto:ignasi.barr...@gmail.com] Sent: 11 March 2014 08:12 To: Carlos Garcia Ibañez Cc: dev; u...@jclouds.apache.org Subject: RE: [jclouds/abiquo issue] The vDC soft limits cannot be forced in version 2.6 of the API Thanks for taking care or this, Carlos! Could you upload your changes to a branch in GitHub so I can have a look? If you can do that I'll upgrade the provider to properly use the 2.6 API (as AFAIK there are no other users using it with a 2.4 version) continuing your work. Thanks! I. El 11/03/2014 08:08, "Carlos Garcia Ibañez" <carlos.gar...@emea.nec.com<mailto:carlos.gar...@emea.nec.com>> escribió: Good morning everyone. I've implemented the changes suggested by Ignasi and I've built a patched version of the org.apache.jclouds.labs-abiquo artefact locally, in order to make use of the version 2.6 of the Abiquo API. Everything seems ok, but I'd like to know when (or if) the jClouds plugin will support this version of the API in order to point my repo to that branch (currently I'm pulling from jclouds/1.7.x). Besides, I'm planning to deploy the patched artefact to our local Nexus, in order not to use the official releases for the moment, but I'm not sure if it is the best practice. Thanks in advance and kind regards. From: Ignasi Barrera [mailto:ignasi.barr...@gmail.com<mailto:ignasi.barr...@gmail.com>] Sent: 05 March 2014 16:52 To: Carlos Garcia Ibañez Cc: u...@jclouds.apache.org<mailto:u...@jclouds.apache.org>; d...@jclouds.incubator.apache.org<mailto:d...@jclouds.incubator.apache.org> Subject: Re: [jclouds/abiquo issue] The vDC soft limits cannot be forced in version 2.6 of the API Enums were deprecated, in favor of a better pluggable platform, and replaced with Strings. You could keep locally the enums and use the name() wherever the enum was used. On 5 March 2014 16:48, Carlos Garcia Ibañez <carlos.gar...@emea.nec.com<mailto:carlos.gar...@emea.nec.com>> wrote: Thank you for your quick response, Ignasi. I've just updated the pom, but some classes are missing, mostly enumerated types (like HypervisorType, TaskType and DiskFormatType). Do you know where I can find them? For the rest of the compilation errors, I think I'll take an aggressive approach, just to have a patched version as soon as possible :) From: Ignasi Barrera [mailto:ignasi.barr...@gmail.com<mailto:ignasi.barr...@gmail.com>] Sent: 05 March 2014 15:31 To: Carlos Garcia Ibañez Cc: u...@jclouds.apache.org<mailto:u...@jclouds.apache.org>; d...@jclouds.incubator.apache.org<mailto:d...@jclouds.incubator.apache.org> Subject: Re: [jclouds/abiquo issue] The vDC soft limits cannot be forced in version 2.6 of the API Hi Carlos, The provider assumes an Abiquo 2.4, and unfortunately I haven't had time to update it. However, you could try upgrading the "api-model-transport" dependency to "2.6.0", which already comes with the new flag. Other things may break, as the model classes in that version are aligned with 2.6, but fixing them should be pretty straightforward. Also executing the live tests will give good feedback too. Could you try it and share the results? On 5 March 2014 15:11, Carlos Garcia Ibañez <carlos.gar...@emea.nec.com<mailto:carlos.gar...@emea.nec.com>> wrote: Hi all. I've just opened an issue in Jira (JCLOUDS-488<https://issues.apache.org/jira/browse/JCLOUDS-488>) regarding the problem we are facing since we changed to the version 2.6 of the Abiquo API: We have recently migrated to the version 2.6 of the Abiquo API. In this version, in order to force the vDC soft limits when deploying a new VM, the flag forceVdcLimits must be set to true. Currently, the VirtualMachine class does not allow to specify such flag when invoking the deploy() method. Moreover, the underlying VirtualMachineTaskDto class used to execute the operation does not accept this flag neither, but this class is located in the api-model-transport dependency, and I wonder how this change request should be managed. As mentioned, some of the changes should be made in the api-model-transport dependency (currently, version 2.3.0), so I wonder if there is a simple workaround for getting the expected behaviour. Any ideas? Any suggestion will be appreciated. Thanks a lot and kind regards. Click here<https://www.mailcontrol.com/sr/rCU1fFLEqVDGX2PQPOmvUg0KooX!PhOyAT96avYCdmmDeBnex!BfyJLZ0vP4Fqhr9cAo+ZZigFDCP4z!bwErJQ==> to report this email as spam.
