Hello,
This is the second release candidate for Apache jclouds 2.1.0.
Please use the separate [DISCUSS] thread for anything but votes.
It fixes the following issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?versi
on=12334714&styleName=Html&projectId=12314430
*** Please download, t
This thread is for discussion of the second release candidate for Apache
jclouds 2.1.0.
Please use this thread for discussion of issues uncovered in the RC,
questions you may have about the RC, etc.
If you want to help to validate the release, you'll find a set of scripts
and the corresponding in
+1, ran verification script and integration tests against blobstores.
On Mon, Feb 12, 2018 at 11:57:05AM +0100, Ignasi Barrera wrote:
> Hello,
>
> This is the second release candidate for Apache jclouds 2.1.0.
>
> Please use the separate [DISCUSS] thread for anything but votes.
>
> It fixes the
Blobstore integration tests show similar results to 2.0.3 and much
improved over 2.1.0-rc1. We have some new tests for storage classes
that show a number of expected failures against DreamObjects (S3 clone)
which does not support this feature.
On Mon, Feb 12, 2018 at 11:58:25AM +0100, Ignasi Barr
I'm afraid I found an issue with rc2 for openstack; although we put a huge
effort to support neutron from nova for security groups management,
jclouds-nova is not able to deal with floating ip when managed by Neutron
instead of Nova.
I think this is a -1
On Mon, Feb 12, 2018 at 1:55 PM, Andrew Ga
-1 votes are release vetoes so I'll cancel the vote in a while.
It's kinda frustrating to find issues like this in Nova after such an
amount of time testing it and after almost an entire RC1 verification cycle.
Cutting a release takes a considerable amount of time and volunteer effort.
It is not
There was a -1 vote cast to the DISCUSS thread, I assume by mistake.
This vote is being canceled due to issues uncovered during validation.
A new release candidate will be created once these issues have been
addressed.
Thank you,
I.
On 12 February 2018 at 13:52, Andrew Gaul wrote:
> +1, ran v
Thanks Ignasi for your help.
Really sorry about the issue encountered only now, but I've been running
RC2 against a new openstack provider and I've found a different situation
compared to the ones I've seen so far.
I will try to fix the issue as quickly as possible, although it is another
tricky
