Re: Switched to jclouds 1.8.1!

2014-12-24 Thread Imesh Gunaratne
Thanks for the information Raj, shall we add this to a README file under this module? IMO each forked module should have a README file mentioning the changes we have done, any pull requests given, etc. Thanks On Wed, Dec 24, 2014 at 7:38 PM, Rajkumar Rajaratnam wrote: > s/Once we upgrade *jclou

Re: Switched to jclouds 1.8.1!

2014-12-24 Thread Rajkumar Rajaratnam
s/Once we upgrade *jclouds to 1.8.1*, we can safely remove the clone/Once we upgrade *to next jclouds version*, we can safely remove the clone Thanks. On Wed, Dec 24, 2014 at 7:34 PM, Rajkumar Rajaratnam wrote: > Hi Imesh, > > Jclouds neutron bundle's manifest is malformed, hence it is not load

Re: Switched to jclouds 1.8.1!

2014-12-24 Thread Rajkumar Rajaratnam
Hi Imesh, Jclouds neutron bundle's manifest is malformed, hence it is not loaded into OSGi runtime. I conveyed this to Jclouds team and they fixed it. But it will not be back ported to 1.8.1 soon. Hence I had to clone neutron api to stratos code base. Once we upgrade jclouds to 1.8.1, we can safel

Re: Switched to jclouds 1.8.1!

2014-12-24 Thread Imesh Gunaratne
Hi Raj, What is the reason for forking openstack-neutron module? Do we have any local changes? Thanks On Wed, Dec 24, 2014 at 12:14 PM, Imesh Gunaratne wrote: > Great! Thanks Raj! > > On Wed, Dec 24, 2014 at 10:05 AM, Rajkumar Rajaratnam > wrote: > >> Hi Imesh, >> >> We have been using this v

Re: Switched to jclouds 1.8.1!

2014-12-23 Thread Imesh Gunaratne
Great! Thanks Raj! On Wed, Dec 24, 2014 at 10:05 AM, Rajkumar Rajaratnam wrote: > Hi Imesh, > > We have been using this version (1.8.1) for a long time now :) > > We haven't encounter any issues with this upgrade so far. Hence I dropped > jclouds 1.8.0 clone as we are not using this anymore (1.8

Re: Switched to jclouds 1.8.1!

2014-12-23 Thread Rajkumar Rajaratnam
Hi Imesh, We have been using this version (1.8.1) for a long time now :) We haven't encounter any issues with this upgrade so far. Hence I dropped jclouds 1.8.0 clone as we are not using this anymore (1.8.0 clone was there, but we didn't use it). Thanks. On Wed, Dec 24, 2014 at 9:45 AM, Imesh

Re: Switched to jclouds 1.8.1!

2014-12-23 Thread Imesh Gunaratne
Thanks Raj! We might need to do a round of testing in OpenStack and EC2 with this jclouds version. On Tue, Dec 23, 2014 at 10:01 AM, Rajkumar Rajaratnam wrote: > Dropped in a9834e9ec1c7c9056fb36dbfcf18bc3fd73087bc > > Thanks. > > On Tue, Dec 23, 2014 at 8:41 AM, Rajkumar Rajaratnam > wrote: > >

Re: Switched to jclouds 1.8.1!

2014-12-22 Thread Rajkumar Rajaratnam
Dropped in a9834e9ec1c7c9056fb36dbfcf18bc3fd73087bc Thanks. On Tue, Dec 23, 2014 at 8:41 AM, Rajkumar Rajaratnam wrote: > Hi Devs, > > I guess we can remove jclouds 1.8.0 clone from stratos code base now. I > have upgraded to jclouds 1.8.1 sometimes back and working fine without any > issues. >

Re: Switched to jclouds 1.8.1!

2014-12-22 Thread Rajkumar Rajaratnam
Hi Devs, I guess we can remove jclouds 1.8.0 clone from stratos code base now. I have upgraded to jclouds 1.8.1 sometimes back and working fine without any issues. So lets drop jclouds 1.8.0 clone. Thanks. On Wed, Dec 3, 2014 at 11:35 PM, Rajkumar Rajaratnam wrote: > Hi Devs, > > I have switc

Switched to jclouds 1.8.1!

2014-12-04 Thread Rajkumar Rajaratnam
Hi Devs, I have switched the master branch to use jclouds 1.8.1 I already have tested with 4.0.0 branch and it was working fine. However, please let me know if you find issues in creating instances and allocating resources (IP and volume) to them. Thanks. -- Rajkumar Rajaratnam Committer & PM